Related
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
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
duraaraa said:
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei.
It's just a preliminary build so I can't promise anything/everything will work! Keep that in mind. I'm not responsible if you brick your device.
EDIT: Does not work with Mate 10 series.
DOWNLOAD LINK:
https://drive.google.com/open?id=0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei/comments/75uwkd/october_12_first_official_android_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you've got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don't mess around too much with TWRP, to be sure you don't brick your system!
Click to expand...
Click to collapse
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
AndDiSa said:
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
Click to expand...
Click to collapse
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
I've tried flashing the entire update.zip file in TWRP...but as noted TWRP is unable to mount internal storage. I'm not sure if I need to wipe and reformat first. I also have no clue whether the TWRP build I installed is properly compatible with the device. I had nothing to lose by giving it a shot.
thref23 said:
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
Click to expand...
Click to collapse
This will not work as the boot chain will be broken due to mismatching checksums. You need to have the correct images. To flash a OTA image you also need to have the standard recovery image installed ...
So...will someone correct please correct me if this is wrong?
If I were to flash a c00 oeminfo file, I could then install a c00 update.zip via dload folder?
Would c432 work as well (with a flashed oeminfo), even though the Euro hardware has different bands than my hardware?
There is now a full OTA on FF for C635.....still nothing for c636...
Finally, a full OTA is available for c636.
But the 'dload' method (update.app on an sd card) failed at 5%. And flashing ramdisk/recovery/erecovery/system images also failed.
Is this possibly because the OTA is B153, whereas my M5 was shipped B121?
(I hate to be that guy bumping his own thread, sorry)
I'm unbricked!
For those in a similar spot, looking to rebrand, or otherwise interested...
I finally e-mailed Funky Huawei for assistance. Their unbrick tool did not work. However, their e-recovery method worked perfectly (basically, you point your router's DNS to Funky Huawei, enter stock recovery and connect to wi-fi, and Funky Huawei's servers mimic Huawei's servers. If they do not have your firmware on their server, they will add it by request (provided it exists on the internet).
I paid $65 for a 30 day pass - a little steep, but I was impatient. I'm not sure if I could have gotten away with paying less. If you want to try and use my FH account over the next 30 days PM me (although I don't want to get carried away with that).
For those looking to rebrand, if you can flash an OEMinfo file successfully (FH has a rebrand tool and I have no clue how well it works), you should be able to use FH's erecovery method to flash firmware (don't blame me if something goes wrong).
One reason for the trouble I was having, if because I bootlooped after making a change to the vendor/build.prop file. This file was on the vendor partition, not the system partition, and for whatever reason the vendor partition cannot be flashed via fastboot (in theory it can be flashed, in reality it returns an error that doesn't have to do with the size of the partition).
Before reverting to FH, I finally got TWRP installled and functioning, and after all the attempts I made to recover my device, the same build.prop file which initially caused a bootloop was still in the /vendor folder. And TWRP wouldn't mount the system and vendor partitions as read/writeable - that was frustrating.
Now off to experiment with AOSP GSIs while I feel like I have little to lose...
Please help me
hello everyone,
i tried to rebrand my m5pro with help of ministryofsolutions. Something went wrong and my tablet (CMR-AL19) is stucked in the recovery mode. how can i fix it? Someone who ca help me? I will pay
Greeztings
Luigi
thref23 said:
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
Click to expand...
Click to collapse
Hello, and thanks for reading my post...HOPING someone can help...so, Here's the specs. If you need more just ask...
Mediatek MT6739 salable: ZTE Z3351S (Qlink Wireless govt. phone)
Android 9 running SP 2019-07-05 (API 28)
Build: Z3351SV1.0.0B4
BL: Locked, no root (even through Magisk...so far.)
As this is my primary phone I'd really rather avoid the off chance of bootloop, soft/hard bricking....but I am very interested in the security features on this device...I've not done a LOAD of rooting and playing, this system has managed to make my poor old brain swim like I had a green beer!!!
I've so far managed to get a temp root solution, and got backups of the entire device excepting the /user partition...not an easy task, and I PROBABLY coulda got it but that's one big-a^& file!
Since I don't wanna have to actually pay full price for a replacement in the case of me screwing up, I've hesitated on trying the Magisk solution for a /system-less root. I unpacked the boot.img and ramdisk (which wound up empty,) and the recovery.img and ramdisk (which did have files,) and I dont really have the experience in repacking the image (with oem signature,)
or (and this is a big one,)
how to enable the full fastboot on it...and I'm not sure where that is, I think it's moved to the user area...and I want the BL unlocked before I even try to Magisk this puppy...
Fastboot works okay, maybe. Command adb reboot bootloader gets me a fastboot mode on the device, but no fastboot devices. When I lsusb (Linux Mint 18) the Mediatek device shows up, but not as bootloader.
I would like to take these unpacked files, mod the existing kernel to allow full fastboot, repack it (with oem sig so the stock recovery doesn't reject it,) the flash it as an update....
....HEEELLLPPP...
What do I do from here?!?
Thanks a LOT guys...and you gals too!:laugh:
My question is how do I flash it back to stock I tried just flashing the kernel back to it like someone suggested but I'm getting a lot of cant load file cannot determine image file name I'm new to this I used Odin a bit with samsung is there such a tool for the nord the problem I think was my phone updated while waiting for the token and I think I got my patch file before I unlock the bootloader then turn around and mixed it up with the boot image I made after unlocking the bootloader I've already wiped it clean I didn't back it up because it was clean I figured I had the md5
Look inside here:
OnePlus Nord Flash File Firmware (Stock Rom) Free Download
OnePlus Nord Firmware Flash File can be used for fixing hang on the logo or removing all screen locks. This file will erase FRP and Pattern, Password lock
www.gadgetsdr.com
Thankyou
5ggggg said:
My question is how do I flash it back to stock I tried just flashing the kernel back to it like someone suggested but I'm getting a lot of cant load file cannot determine image file name I'm new to this I used Odin a bit with samsung is there such a tool for the nord the problem I think was my phone updated while waiting for the token and I think I got my patch file before I unlock the bootloader then turn around and mixed it up with the boot image I made after unlocking the bootloader I've already wiped it clean I didn't back it up because it was clean I figured I had the md5
Click to expand...
Click to collapse
If everyone wasnt so intrested in making someone feel dumb or looking like a smart pants all this jibberish could be explained easy I'm sure but I like so many other people that have been stuck dealing with this issue will have to just move on to another phone I hope this post helps someone avoid all these how to s that just leave you with a screwed up phone
I was trying to bypass Google FRP lock on this phone, after having no success, I went online looking and downloaded Rom2Box to try to bypass frp.. When I was trying to get the program to discover my device, nothing happened, it never discovered it, but while it was attempting to discover it, my phone had a black screen with a red dot and 2 smaller white dots moving around the red dot in a circle pattern while bumping off of each other.. I don't know what it means, I never saw it before.. .. Now it won't turn on, or show that it's being charged so I think this program bricked my phone..?
I guess I'd like to give Odin a shot at fixing it for me.. But I don't know Odin, I never messed with phone's like this.. Is, this my best or only option?
Try MSM Tool
@Princess007 I've got the newest ROMt2Box .. if you need it.
@ScarletWizard
Firmware - https://mega.nz/file/EDwAAAIB#hUVmdbWUFI0bt0WQZVfaenTfVwoOqlfn2oexY5uC-Hs
romtoolboxpro - https://mega.nz/file/tTBSGagI#nYvCwk_prTrkM2E3VGk7Sh9qqw5NCn1PZhc73oxrl6U
Samsung Touch sensitivity is very Awesome..
Where can i find the firmware for oneplus nord n20 5g T-Mobile, current build number is GN2200_11_A.07?
Trying to extract boot.img and patch with Magisk
I can pull a rooted super and should have those already actually but if your system is not already magisk patched then you will not be able to boot. I have lost the stock July somewhere in all my backups but I'm willing to pull the boot and super for you if you need it. It is already RW system
Princess007 said:
I was trying to bypass Google FRP lock on this phone, after having no success, I went online looking and downloaded Rom2Box to try to bypass frp.. When I was trying to get the program to discover my device, nothing happened, it never discovered it, but while it was attempting to discover it, my phone had a black screen with a red dot and 2 smaller white dots moving around the red dot in a circle pattern while bumping off of each other.. I don't know what it means, I never saw it before.. .. Now it won't turn on, or show that it's being charged so I think this program bricked my phone..?
I guess I'd like to give Odin a shot at fixing it for me.. But I don't know Odin, I never messed with phone's like this.. Is, this my best or only option?
Click to expand...
Click to collapse
this usually happens because some component of your device is not loading due to either mismatched security pacthes, some system partition has been altered and cannot load or one of many other reasons. i have a device that works perfectly fine and boots with this oneplus logo rather than the tmobile splash that it used to boot with. for me this was caused by mixing components from different systems. i had to flash matching radios, boot, and system, vbmeta disabled to get the device to function with mismatched partitions but the only thing thats still not working is the tmobile splash, which i dont miss and have no desire to try to fix that so i have been running this device in that state for months with 0 problems other than when one of my mods breaks the system and i just have to undo whatever i modified and im back to a functioning state. thedot with 2 dots bouncing around it is fine so long as everything else works, just means that something in vendor is probably different than what it expects so that part doesnt load or some other partition..... disabling verity and verification can usually get me booting again if this happens whether everything else works and is important to you is your decision to fix it or not. going back stock should fix it all. best thing to do if ur gonna mod is make sure u pull backups of EVERY single partition on the device so you have matching images. would suck to lose efs partitions because they are unique and the only people that can get those back for you is the manufacturer
i recommend using partitions backup & restore from playstore. its free and you can pull all of your partitions for restoring in the future. i recommend setting the options to save as raw(.img) rather than archives and then after it pulls all of them, compress them all into one archive. this will save you from having to extract each image from 100 different archives if you need to do a full restore in the future. best of luck and thanks for your contribution
Glitchmob2640 said:
Where can i find the firmware for oneplus nord n20 5g T-Mobile, current build number is GN2200_11_A.07?
Trying to extract boot.img and patch with Magisk
Click to expand...
Click to collapse
theres alread an a.07 boot image posted thats already been patched. best to pull your own but if your gonna use one thats not pulled directly from your device you may as well just use the one thats already patched. i have attached the magisk-delta patched boot image that i use on my july device GN2200_11_A.07
magisk-delta patched boot image that i use on my july device GN2200_11_A.07
T-Mobile MSM tool
File folder on MEGA
mega.nz
DrScrad said:
T-Mobile MSM tool
File folder on MEGA
mega.nz
Click to expand...
Click to collapse
can someone post a link for the msmtool for the N20 from T-Mobile, this link is dead
Is there an MSM tool for the Metro version of the Nord N20 5G? I can't seem to find one anywhere.
ScarletWizard said:
Download MSM Download Tool: Unbrick any OnePlus Device [Video]
From this guide, you could download the MSM Download Tool for every OnePlus device and then use it to unbrick your OnePlus device.
www.droidwin.com
Click to expand...
Click to collapse
That one ain't gonna work.. you've gotta download the newest tool..
NewVersion_2.exe
drive.google.com
Does anyone have a link to just the msm tool without the rom?
I've got the rom, but no working tool, and I don't have the internet to download a whole other rom