Hello everyone.
I know many of you have worked on safe-strap TWRP recovery in light of the inability to unlock the bootloader.
I have been testing on my note 8 and as someone else pointed out if you install the Engineering Rom listed below you will have the oem unlock toggle.
This service rom.
COMBINATION_FA71_N950USQU2AQK3_CL12591988_QB15811772_REV00
As far as everyone believes this option is only for FRP reset.
To tell you anyway the FRP reset is simply ZEROing out the persistence partition.
A persistence partition that is ZERO is default OEM Unlock ON. Meaning the toggle is set to not allow oem unlocking.
Using the mentioned rom above it is possible to set oem unlocking allowed.
This does not mean the bootloader is unlocked.
But i do feel that it is very close to unlocked and leads me down a path that i can unlock the bootloader.
I have a Galaxy Tab E that is allowed to be bootloader unlocked.
By doing a dd dump of all partitions then doing hexdump of the dd dumps the hex dumps can be diffed in terminal effectively.
By doing a comparison of the unlocked and locked state partitions I can Identify the changes being made.
I am still in the process of testing and comparing the dumps.
I need a TWRP build for N950USQU2AQK3 or ver 2 bootloader.
I almost think I have the bootloader set to where it will allow TWRP to Run.
This may not be a full unlock yet but having a good TWRP build would be a good test.
I could build TWRP myself but i do not have a build system setup currently..
So one of you that has compiled twrp for safestrap or other testing please share to save me some time.
I dealt with this same scenario on a HTC Desire 526 that was bootloader locked by verizon.
I did develop a unlock method using this same process i am using now.
So no......This is not a JOKE.
I am making progress on unlocking the note 8 USA Variety. :victory:
Help me out and share your TWRP.
HI, I have a SM-N950U and I'm on Verizon,
My Baseband is:
N950USQU1AQI5
What would you like someone to do for you?
Htc is different then samsung....samsung has checks on every partition in the device if it detects something the phone will not boot ha
pbedard said:
Htc is different then samsung....samsung has checks on every partition in the device if it detects something the phone will not boot ha
Click to expand...
Click to collapse
Bigcountry has been doing all the necessary research which involves how the partitions interact with each other. He is really close to officially unlocking the boot loader apparently. We all are aware of how strict Samsung is but there seems to be a small window of opportunity that WILL enable a true bootloader unlocking method.
JedidroidX said:
Bigcountry has been doing all the necessary research which involves how the partitions interact with each other. He is really close to officially unlocking the boot loader apparently. We all are aware of how strict Samsung is but there seems to be a small window of opportunity that WILL enable a true bootloader unlocking method.
Click to expand...
Click to collapse
ºȯº could it be?
Wow really this would be awesome. Cannot wait. Thanks for the hard work.
I really hope this works
Interesting
I am still making progress on this. I took a step back to make sure I can unbrick my device when I screw something up.
Currently I am working on the unbrick for the V2 bootloader.
Someone got the firehose for the s-8 and s-8 + versions and some people have had luck unbricking s8 and s8+.
I have to rebuild the s8 unbrick rom for the note 8.
This involves getting the GPT tables off the device then decoding the GPT to write the partition.xml. Since we have ufs memory there are 4 primary partitions which means there are 8 GPT tables.
Once I have this all completed we can flash anything we want with the firehose. Even single partitions.
What I was asking for was TWRP that is Built for the Note 8.
So I can see if I can get it to boot.
This would save me from building TWRP myself and leave me more time to work on other stuff.
My Note 8 is currently on V2 bootloader.
We will need a unbrick rom for each bootloader version.
In order for me to make that I will need the GPT tables from each bootloader version. I can provide the commands to do it. Anyone wanting to help just let me know. I will be starting a new thread of how to do this soon.
BigCountry907 said:
I am still making progress on this. I took a step back to make sure I can unbrick my device when I screw something up.
Currently I am working on the unbrick for the V2 bootloader.
Someone got the firehose for the s-8 and s-8 + versions and some people have had luck unbricking s8 and s8+.
I have to rebuild the s8 unbrick rom for the note 8.
This involves getting the GPT tables off the device then decoding the GPT to write the partition.xml. Since we have ufs memory there are 4 primary partitions which means there are 8 GPT tables.
Once I have this all completed we can flash anything we want with the firehose. Even single partitions.
What I was asking for was TWRP that is Built for the Note 8.
So I can see if I can get it to boot.
This would save me from building TWRP myself and leave me more time to work on other stuff.
My Note 8 is currently on V2 bootloader.
We will need a unbrick rom for each bootloader version.
In order for me to make that I will need the GPT tables from each bootloader version. I can provide the commands to do it. Anyone wanting to help just let me know. I will be starting a new thread of how to do this soon.
Click to expand...
Click to collapse
I have a V3. I also am currently learning some arm assembly this semester, so I might be of some (minor) use. Note sure what my schedule will allow, but I will definitley assist how I can.
BigCountry907 said:
I am still making progress on this. I took a step back to make sure I can unbrick my device when I screw something up.
Currently I am working on the unbrick for the V2 bootloader.
Someone got the firehose for the s-8 and s-8 + versions and some people have had luck unbricking s8 and s8+.
I have to rebuild the s8 unbrick rom for the note 8.
This involves getting the GPT tables off the device then decoding the GPT to write the partition.xml. Since we have ufs memory there are 4 primary partitions which means there are 8 GPT tables.
Once I have this all completed we can flash anything we want with the firehose. Even single partitions.
What I was asking for was TWRP that is Built for the Note 8.
So I can see if I can get it to boot.
This would save me from building TWRP myself and leave me more time to work on other stuff.
My Note 8 is currently on V2 bootloader.
We will need a unbrick rom for each bootloader version.
In order for me to make that I will need the GPT tables from each bootloader version. I can provide the commands to do it. Anyone wanting to help just let me know. I will be starting a new thread of how to do this soon.
Click to expand...
Click to collapse
I'm on bootloader 5. I'll be glad to help ya out with what you need.
BigCountry907 said:
I am still making progress on this. I took a step back to make sure I can unbrick my device when I screw something up.
Currently I am working on the unbrick for the V2 bootloader.
Someone got the firehose for the s-8 and s-8 + versions and some people have had luck unbricking s8 and s8+.
I have to rebuild the s8 unbrick rom for the note 8.
This involves getting the GPT tables off the device then decoding the GPT to write the partition.xml. Since we have ufs memory there are 4 primary partitions which means there are 8 GPT tables.
Once I have this all completed we can flash anything we want with the firehose. Even single partitions.
What I was asking for was TWRP that is Built for the Note 8.
So I can see if I can get it to boot.
This would save me from building TWRP myself and leave me more time to work on other stuff.
My Note 8 is currently on V2 bootloader.
We will need a unbrick rom for each bootloader version.
In order for me to make that I will need the GPT tables from each bootloader version. I can provide the commands to do it. Anyone wanting to help just let me know. I will be starting a new thread of how to do this soon.
Click to expand...
Click to collapse
I'm on v3 bootloader...if you need anything I will try my best to help you out and see if we can get this phone unlocked
I'm interested and will get note 8 for this work. Is there any particular bl you'd prefer like rev1 and or 3 or just rev 2. Also I have a Samsung edl tool to aid the firehose process. Now that I think of it I already have firehose Rev2 from when I bricked out on SD.
---------- Post added at 06:10 PM ---------- Previous post was at 06:01 PM ----------
Also what sort of programming knowledge can help you if you don't mind me asking
Vell123 said:
I'm interested and will get note 8 for this work. Is there any particular bl you'd prefer like rev1 and or 3 or just rev 2. Also I have a Samsung edl tool to aid the firehose process. Now that I think of it I already have firehose Rev2 from when I bricked out on SD.
---------- Post added at 06:10 PM ---------- Previous post was at 06:01 PM ----------
Also what sort of programming knowledge can help you if you don't mind me asking
Click to expand...
Click to collapse
Currently I am working on Rev 2. bootloader.
You guys that have other Revisions Can help us all out by getting GPT backups from your devices. Then I can Compare the GPT for differences.
I currently have the UNBRICK for bootloader version 2.
Anyone with a HARD Bricked device that is on samfail V2 possibly samfail V2..5 or the factory AQK2 or the AQK2 factory repair should test this unbrick. I am sure it will work.
If other versions of the bootloader have the same gpt then we can take the bootloaders out of the stock firmware and swap them with the files in the unbrick and it should work. If the gpt is different then new GPT files will need made for the other bootloaders.
@Vell123;77796726
Which Box do you have?
You mention SD / does the sdcard method still work.
Do you put the sdcard into the device to boot download mode?
If that is the case we can run full android off the sd card potentially.
I would love to have a copy of the card if you can dd and image that would be great.
I have been thinking about buying the medusabox pro. It supports firehose and these phone models.
I don't know what box is best but whatever it is i want to buy one.
As far as bootloader unlocking I noticed after the GPT on the beginning of dev/block/sda there is a pretty decent chunk of data that is not the GPT or the PIT and may be a place for us to look into. Its basically a hidden spot in the emmc that samsung is not normaly written to.
@kronickhigh
If you can re-base and disassemble the abl.img that could lead us down the right road. You may be able to locate where the security checks are executed. If you can locate those it could be possible to determine the memory addresses where this data is stored.
I'm going to start a new thread on GPT and I will post there the commands to pull the GPT and what were looking at.
I am also going to start a new thread for the unbrick files.
@Vell123;77796726
If you can share the sdcard image you have that would be superb.
For now here is the v2 unbrick tor the N950U
Which Box do you have? I have the z3x box however i also have a edl repair cable/tool.
You mention SD / does the sdcard method still work.
Do you put the sdcard into the device to boot download mode? I don't have a SD card version. I was told by Me21( that made Samfail ) it wouldn't work so i didn't mind working on anything. However it might work. When i said SD i was referring to Snapdragon processors.
If that is the case we can run full android off the sd card potentially.
I would love to have a copy of the card if you can dd and image that would be great.
I have been thinking about buying the medusabox pro. It supports firehose and these phone models.
I don't know what box is best but whatever it is i want to buy one.
I'm sure your may already know the boxes use AT+COMMANDS but the most support is the best!
As far as bootloader unlocking I noticed after the GPT on the beginning of dev/block/sda there is a pretty decent chunk of data that is not the GPT or the PIT and may be a place for us to look into. Its basically a hidden spot in the emmc that samsung is not normaly written to.
@kronickhigh
If you can re-base and disassemble the abl.img that could lead us down the right road. You may be able to locate where the security checks are executed. If you can locate those it could be possible to determine the memory addresses where this data is stored.
I'm going to start a new thread on GPT and I will post there the commands to pull the GPT and what were looking at.
I am also going to start a new thread for the unbrick files. @Vell123;77796726
If you can share the sdcard image you have that would be superb.
For now here is the v2 unbrick tor the N950U[/QUOTE]
Rip note 8
What Happened
pbedard said:
Rip note 8
Click to expand...
Click to collapse
What happened to your note 8.
The unbrick files are legitimate Samsung Leaked files.
If you are on bootloader rev 2 you should be able to unbrick it.
You need to load the qualcomm edl drivers.
If you are on a different bootloader version we can try to make a unbrick for you.
Also depending on what you were doing.
You may have got the device stuck in sahara mode or something.
I once thought i bricked mine.
It was deader than dead. Only showed up as unrecognized device.
I left it that way overnight until the battery fully died.
Then when i plugged it in the next day it came back to life.
Unless you physically damaged the note 8 it can be recovered. Sooner or later.
Sooner if you are on rev 2
So as this thread first asked.
Who has a halFway decent tree for me to build TWRP.
I going to need it pretty soon.
Were about there. I gotta get me a 64gb sd card tonight and finish up a little more work on my gpt decoder.
Looking at the strings in the elf files I can see that the option to boot from sd card is in there.
Other than that I need to create sparse chunk images of partitions like /system and /data and /persist.
All the big boys gotta get sparsed out to chunks small enough for edl flashing.
I have a very special set of bootloaders and I'm thinking this set will be able to be unlocked.
What needs done is building a complete edl flash using these bootloaders and the standard U2 version /system and other images needed to complete the flash. If this all works as I anticipate it will be RIP Locked Bootloader.
I am on rev 3 i fixed my bricked device myself with a friends help
BigCountry907 said:
So as this thread first asked.
Who has a halFway decent tree for me to build TWRP.
I going to need it pretty soon.
Were about there. I gotta get me a 64gb sd card tonight and finish up a little more work on my gpt decoder.
Looking at the strings in the elf files I can see that the option to boot from sd card is in there.
Other than that I need to create sparse chunk images of partitions like /system and /data and /persist.
All the big boys gotta get sparsed out to chunks small enough for edl flashing.
I have a very special set of bootloaders and I'm thinking this set will be able to be unlocked.
What needs done is building a complete edl flash using these bootloaders and the standard U2 version /system and other images needed to complete the flash. If this all works as I anticipate it will be RIP Locked Bootloader.
Click to expand...
Click to collapse
Fingers crossed and good luck!
Related
EDIT: no longer need this. It is possible to make your own...
There is a chance that I may not have fried my V10 by shorting the test point, but to test that I need a full Nougat dump (something I can not believe I didn't make from my own phone -- I only have a full MM dump).
If there is someone that has rooted Nougat AND flashed all the Nougat partitions (v30b_update.zip and full_nougat.zip), and is willing to do a full dump, please let me know.
It is preferable if you have access to Linux because you will need to null out some partitions that have private data, and it is much easier to explain how to do it on Linux.
Lastly, this image will be 64gigs uncompressed, but it compresses very well.
Thanks,
-- Brian
Wish I can help, but mine is not rooted..
Hopefully I can bring my phone back to life (one way or another) so I can continue on. I got my board of eBay, but it was more dead than my current board.
runningnak3d said:
Hopefully I can bring my phone back to life (one way or another) so I can continue on. I got my board of eBay, but it was more dead than my current board.
Click to expand...
Click to collapse
That sounds bad. Hopefully someone will upload it.
if i can downgrade it , ill re upgrade to rooted nougat and get a dump but i dont know how to dump and dont have the image for downgrade.
@runningnak3d There's a guy selling one in General. Perhaps you can get a dump off of him?
@runningnak3d I currently have one V10 that I cannot get past the Checking Updates screen in the setup wizard on Nougat (with TWRP) which I am considering performing a KDZ wipe and another that went black screen after I flashed MM (also with TWRP). If I do a KDZ wipe on the first one, I could do a dump for you but I would have to look up how to. You are also welcome to buy the board from the second V10 from me but I'm unsure if you can revive it.
Thanks all, but everything I needed to make my own was staring me in the face.
-- Brian
i will help if i can , but didnt have root yet
@runningnak3d I'm in a need of a Nougat dump for H901, to make a bootable sdcard. Could you share yours or guide how to make one from nougat kdz?
Due to messing the aboot partition (while trying to shut the "big cores" off) the phone does not boot, nor enter download mode. On powering on, it only vibrates. QPST does not work with the phone put into 9008, it returns "target may be unstable". Before that, the phone was rooted, with bootloader unlocked, updated to nougat via the recovery, with the ZIPs.
Any help would be greatly appreciated
Be glad to, and it is easy, but you need dd. If you use Windows, there may be some program that can do something similar, but I haven't used Windows in years. You can always install a very basic Cygwin environment...
* Insert 64gig SD card
* Dump KDZ
* dd if=PrimaryGPTxxxxxx of=/dev/mmcblk0
The xxxxx above is because I can't remember what it gets dumped as, but it will be obvious.
Once you have the partition table on the sdcard, get a list of the partitons:
* gdisk -l /dev/mmblck0
Then proceed to flash the rest of KDZ onto their individual partitions.
For example, I believe that modem was partition 1, so:
* dd if=modemxxxxx of=/dev/mmcblk0p1
Repeat for every partition from the KDZ except system (unless you want to fully boot from the SD card). Also, you can flash recovery with TWRP, and then you can boot from the SD card to recovery and then you only need to flash your aboot partition, so you don't have to use download mode to flash the entire KDZ.
Let me know if you need me to clarify anything.
EDIT: If you do boot to recovery from the SD card, you will need to make sure to flash the correct device. When you go into an adb shell, you will have two mmcblk devices (mmcblk0 and mmcblk1). I don't remember which will be which, so to be safe flash the aboot partition on both...
-- Brian
@runningnak3d Thank you for your reply! I have Ubuntu 17 as a bootable DVD. Does the sdcard have to be formatted in a specific filesystem before doing this? Another question I have, is that the sdcard shows up as dev/sdd for me but it also shows that dev/sdd1 exists on it, so to which should I dd the GPT table to?
I tried to dev/sdd and wrote the rest of KDZ to the partitions, but the phone has not booted (its 64gb sd hc class 10 card). After dd-ing the PrimaryGPT, the terminal mentions that backupGPT is corrupted and that MBR is protective on the sdcard. Also, GParted shows "unknown" for each partition, and modem partition shows up as fat16 one.
Perhaps I should try different nougat KDZ? the phone's sticker under battery says it's H901, so was written in the phone under settings menu (phone also had t-mobile bloatware) and in LGUP when updating to MM, yet the motherboard has VS990 written on it.
My phone said vs990 on the board as well, so that isn't the issue. You need to flash a few partitions from the phone that aren't in the KDZ ... you will have to get someone to dump them for you.
The only place I had them was on an SD card that I have already wiped since I don't have a v10 anymore.
I will have to look in SBL1 to get you a list that you will have to ask for.
They are all just firmware, and contain nothing specific to a users phone, so anyone with a rooted Nougat phone can safely dump them for you.
Please bear with me. I am currently trying to revive my H910 and I order an H918 that I am going to use to help someone with, but I will try to get you the info ASAP.
H901 VS990 board 9008 brick help
@runningnak3d Hey, you seem like an expert at unbricking V10s. I have a H901 that has vs990 motherboard in it. It bricked while I was updating through LG Bridge. I now only have access to qualcomm 9008 mode.
From my understanding, there are 2 ways to solve this. QFIL or booting from dump image through sdcard. The qfil way didn't work for me, since there aren't any compatible .mbn files and xml for VS990 owners. So my only other option is getting to download mode via sdcard method, and I need the dump files for that. If I do what you've told @Mr_pringle, would my phone enter download mode? What exactly would I have to do? Thanks
@N3XTN3XUS What version were you on, and what version did LG Bridge try to update you to?
runningnak3d said:
@N3XTN3XUS What version were you on, and what version did LG Bridge try to update you to?
Click to expand...
Click to collapse
mm to nougat. Do you have the dump img for mm by any chance?
Unfortunately you are going to have to roll your own with the instructions I gave above.
In order to do that, you need to find out what model you should be flashing. I know you said your board said VS990, I am sitting here looking at my dead board, and it says VS990 on it as well, so H901 Nougat *should* have worked for you. I don't have any idea where you should start looking, but you do need to know that before making an SD card or even if you make a perfectly good card, it won't work
-- Brian
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
Looking to start a discussion on rooting the unlocked version.
I have tried the root for other variants for this phone and does not work
hi would love to see my k8+ rooted. i have the lmx210ulma version mtk and android 7.1.2.
There are recoveries for this phone and i have a full partition dump i nade today using salt on my ubuntu 18.04 machine. when i say full i mean something like 30-50 .img files pulled.
Any way. The problem on my end is booting into fastboot mode or rebooting to the bootloader. i have tried ADB, recovery and key combinations with out ever getting there. I can however get the phone to download into recovery download mode just fine.
any help would be appreciated
https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434
Duhjoker said:
hi would love to see my k8+ rooted. i have the lmx210ulma version mtk and android 7.1.2.
There are recoveries for this phone and i have a full partition dump i nade today using salt on my ubuntu 18.04 machine. when i say full i mean something like 30-50 .img files pulled.
Any way. The problem on my end is booting into fastboot mode or rebooting to the bootloader. i have tried ADB, recovery and key combinations with out ever getting there. I can however get the phone to download into recovery download mode just fine.
any help would be appreciated
Click to expand...
Click to collapse
We are now in this forum. Why some dork mod moves these too early?
Why here, why not to the K8 forums instead?
The link I posted should work with your device...
Just got told to go to the k8 forums because im really just trying to get the bootloader unlocked. Temp root is nice but my plans involve a recovery and a fully rooted phone. Im trhing to develop a way to compile apps and operating systems completely on the device but i need full access.
Im looking for firmware for LG K8 2018 X210ULMG. Where can i find it ?
go to google and type in "LG K8 + LMX210ULM stock rom" you will get at least five pages or more.
Duhjoker said:
go to google and type in "LG K8 + LMX210ULM stock rom" you will get at least five pages or more.
Click to expand...
Click to collapse
I can't fin anywhere for X210ULMG. Try and when you will find paste here link because anywhere is this rom.
which android version do y0u have 9n your k8. I also need you to go to settings system software info and tell me the software versiion. And just for SandG no seriously, open up a terminal in terminal emulator and type getprop. im looking fir the value of
ro.lge.swversion_arb
to be of further assistance may i ask what exactly you are using it for? ie reflash stock fix brick or other. i can help you with the best plan of action and any other how to.
If you are still out there the ULMG and ULM are the same device. There is no ULMG stock rom. So you will need to flash your K8+ using the ULM firmware. If you are looking to roll back to get to the bootloader the lowest version you can find is a letter F version. None so far have an ARB value so happy flashing.
I myself own this device and its an easily rootable phone with bootloader unlock. Just flash the kdz with the lowest letter value then adb reboot bootloader and then in fastboot mode use fastboot oem unlock and your free to flash any cv1 device twrp recovery.img to the phone.
Just make sure to use either carliv image kitchen or android image studio to check and make sure that system, syatem.img, are both ext4 in recovery.fstab. System.img will probably be labled emmc which will cause failure to mount. Also cache and data as well. Firmware/modem should be labled as vfat. Just as if they were labled if you looked at original fstab.
To root just extract boot.img from kdz and patch using magisk and flash using fastboot flash boot boit.img then fastboot flash recovery recovery.img When booting into twrp first time flash no verity opt encrypt and make backup. Upon exiting make sure all parts are mounted or twrp loop will occur.
Duhjoker said:
If you are still out there the ULMG and ULM are the same device. There is no ULMG stock rom. So you will need to flash your K8+ using the ULM firmware. If you are looking to roll back to get to the bootloader the lowest version you can find is a letter F version. None so far have an ARB value so happy flashing.
I myself own this device and its an easily rootable phone with bootloader unlock. Just flash the kdz with the lowest letter value then adb reboot bootloader and then in fastboot mode use fastboot oem unlock and your free to flash any cv1 device twrp recovery.img to the phone.
Just make sure to use either carliv image kitchen or android image studio to check and make sure that system, syatem.img, are both ext4 in recovery.fstab. System.img will probably be labled emmc which will cause failure to mount. Also cache and data as well. Firmware/modem should be labled as vfat. Just as if they were labled if you looked at original fstab.
To root just extract boot.img from kdz and patch using magisk and flash using fastboot flash boot boit.img then fastboot flash recovery recovery.img When booting into twrp first time flash no verity opt encrypt and make backup. Upon exiting make sure all parts are mounted or twrp loop will occur.
Click to expand...
Click to collapse
I have problem because one month ago I flashed My K8 ULMG with kdz for Aristo 2 . I downloaded the software from Aristo 2 and made Brick through it.
Now it doesn't turn on, gives no sign of life, nothing. When connected to a laptop, the computer can only see Qualcomm HS-USB QDLoader 9008.
Do you know solution for it ?
There are two versions of the k8+ a qualcomm version and an mtk version. Did you read my post after your last reply. I was trying to help you determine that sort 0f thing.
As for a fix.... no as of currently there is no fix for either the qc or mtk versions once bricked. i am working on possible solutions but those are not going to be any time soon.
Your best bet at this point is to look for a used and damaged phone and replace the board in your phone with a different board. Find a k8+ lm-x210ulm or an aristo 2 board. They are cheap around $20 us and can be found with broken screens. They have no arb values so can be flashed and downgraded to get the boot loader unlocked and reflashed and upgraded after with guidance.
Dont feel to bad it happens. I have 4 boards that are trash but im still gonna try to unbrick them. But please what ever you do dont do it with out guidance. pm if you need and ill help.
Duhjoker said:
There are two versions of the k8+ a qualcomm version and an mtk version. Did you read my post after your last reply. I was trying to help you determine that sort 0f thing.
As for a fix.... no as of currently there is no fix for either the qc or mtk versions once bricked. i am working on possible solutions but those are not going to be any time soon.
Your best bet at this point is to look for a used and damaged phone and replace the board in your phone with a different board. Find a k8+ lm-x210ulm or an aristo 2 board. They are cheap around $20 us and can be found with broken screens. They have no arb values so can be flashed and downgraded to get the boot loader unlocked and reflashed and upgraded after with guidance.
Dont feel to bad it happens. I have 4 boards that are trash but im still gonna try to unbrick them. But please what ever you do dont do it with out guidance. pm if you need and ill help.
Click to expand...
Click to collapse
Did you found some method for unbrick this phone without motherboard change ?
This is a long-shot but essential if we're going to mess around with this phone with any degree of confidence or YOLO. Without this, there is no experimenting with global non-5G 7T Pro roms and partitions. The MSM for the OP7 Pro 5G for EE and Sprint never leaked, but that was a low-key phone. Let's do better with the T-Mobile McLaren.
Your mission is simple: Obtain the MSMDownloadTool and ops file (usually packaged together in a password-protected rar). You need that package and the password. These are device specific. Don't really care how the files are ultimately delivered as long as there's no encryption. Any info about the file or URL (e.g. https://s3.amazonaws.com/oneplussupport/...) is welcome.
I hate bounties or the thought of enforcing one, but expect donations if you succeed and avail yourself. Anonymity is also acceptable.
If you happen to find something we don't expect like global firmware for this phone, there's a separate bounty thread for that. I doubt it exists.
Relevant codenames and identifiers for our device:
HD1925
hotdogg
oneplus7tpronroxygen
HD61CB
I think @ddggttff3 asked them for this and they wouldn't send it to him for some reason. Maybe they misunderstood what he was asking for? A stock MSM image is just stock, so it doesn't make sense to not release it on XDA. It seems wasteful for a company to have to do extra remote recovery sessions when simply releasing a stock MSM image on XDA could save a company extra time and money.
I also asked OnePlus https://www.oneplus.com/support/contact for a MSM image for the OnePlus 7T Pro 5G McLaren, since it's critical for safe development. In my case, they did not say no, they just gave me a boilerplate response of, "About your concern we would like to inform you that we will take this as feedback and pass it along to our developer team so that this update can be rectified in the upcoming updates in the near future." They emailed me again asking for a further response and I haven't replied yet, because that second email was more obviously automated and did not have a name like the first one did. I think they could possibly let a tech post it to XDA, etc., if convinced by someone with experience like a XDA Recognized Developer.
jhofseth said:
I also asked OnePlus https://www.oneplus.com/support/contact for a MSM image for the OnePlus 7T Pro 5G McLaren, since it's critical for safe development. In my case, they did not say no, they just gave me a boilerplate response of, "About your concern we would like to inform you that we will take this as feedback and pass it along to our developer team so that this update can be rectified in the upcoming updates in the near future." They emailed me again asking for a further response and I haven't replied yet, because that second email was more obviously automated and did not have a name like the first one did. I think they could possibly let a tech post it to XDA, etc., if convinced by someone with experience like a XDA Recognized Developer.
Click to expand...
Click to collapse
I just got off a chat with an agent and they tell me I'll get a remote session with their technical team in 24-48 hours I'm gonna do my best to get the image/ password for you guys
tserv95 said:
I just got off a chat with an agent and they tell me I'll get a remote session with their technical team in 24-48 hours I'm gonna do my best to get the image/ password for you guys
Click to expand...
Click to collapse
Did it work out?
Still waiting from then
They never follow up. I'm still waiting a week later
LLStarks said:
They never follow up. I'm still waiting a week later
Click to expand...
Click to collapse
Same here, been about four days!
Unlucky. OnePlus is being pretty crappy with their service.
https://www.oneplus.com/support/contact has 3 contact options: phone (Call us +1 (833) 777-3633 7x24 hours), live chat and email. I really think a XDA Recognized Developer might have some luck getting a MSM image for the OnePlus 7T Pro 5G McLaren. There is a legitimate safe development need for this and providing it only benefits OnePlus and T-Mobile. The squeaky wheel gets the grease!
Barring actually getting the MSM I may have a method of recovery using fastboot and friends. However, I need the help of
a hotdogg owner with stock firmware & unlocked bootloader. The method is non-destructive (aside from the unlocking nuking
your data); just requires you to use fastboot to boot a twrp image and use adb to pull a partition (its 15gb, so to make it faster
you may want to use a real usb-c 3.0 cable; I don't think the orange one that comes with it is) and unpack it with a tool
called 'lpunpack' (unfortunately I don't know how to build it outside of an aosp/lineageos/grapheneos tree yet).
bad news, after waiting for days for a response from Oneplus, I decided to phone them. They state that after speaking to the remote support team, they cannot even help us. As they apparently don't have the images for the T-Mobile firmware either/ firmware for the Mclaren edition. This is a big bummer as until they (if they for that matter) release the firmware on support site we have no way of really recovering a bricked device and any firmware flashing is gonna be very dangerous to attempt. So yeah.. really regretting buying a T-Mobile variant Oneplus phone atm.
tserv95 said:
bad news, after waiting for days for a response from Oneplus, I decided to phone them. They state that after speaking to the remote support team, they cannot even help us. As they apparently don't have the images for the T-Mobile firmware either/ firmware for the Mclaren edition. This is a big bummer as until they (if they for that matter) release the firmware on support site we have no way of really recovering a bricked device and any firmware flashing is gonna be very dangerous to attempt. So yeah.. really regretting buying a T-Mobile variant Oneplus phone atm.
Click to expand...
Click to collapse
So, does T-Mobile flash the final firmware after OnePlus ships it to the US or something? If the firmware isn't finally flashed until it gets to the US, then that might make sense; but, if not, someone there could either be mistaken or less than truthful.
---------- Post added at 11:24 AM ---------- Previous post was at 10:54 AM ----------
Maybe this will be a good avenue for us? https://twitter.com/tmobilehelp
tserv95 said:
bad news, after waiting for days for a response from Oneplus, I decided to phone them. They state that after speaking to the remote support team, they cannot even help us. As they apparently don't have the images for the T-Mobile firmware either/ firmware for the Mclaren edition. This is a big bummer as until they (if they for that matter) release the firmware on support site we have no way of really recovering a bricked device and any firmware flashing is gonna be very dangerous to attempt. So yeah.. really regretting buying a T-Mobile variant Oneplus phone atm.
Click to expand...
Click to collapse
Do you currently have one in an unflashed (to anything other than stock), unlocked state? If so I can probably guide you through how we can get a sort of
flashable stock image (flashed over fastboot). Hit me up if you are in that situation (sim unlocked, bootloader unlocked, and otherwise stock firmware).
---------- Post added at 11:50 AM ---------- Previous post was at 11:27 AM ----------
jhofseth said:
So, does T-Mobile flash the final firmware after OnePlus ships it to the US or something? If the firmware isn't finally flashed until it gets to the US, then that might make sense; but, if not, someone there could either be mistaken or less than truthful.
---------- Post added at 11:24 AM ---------- Previous post was at 10:54 AM ----------
Maybe this will be a good avenue for us? https://twitter.com/tmobilehelp
Click to expand...
Click to collapse
Quite possible. I don't recall offhand but I believe mine came to me with version 10.0.14, and after 'recovering' from
flashing an experimental lineageos build on mine I ended up on version 10.0.13, which may be sort of the last common
ancestor for all the variants, and its now unable to OTA (it wants to go to 10.0.16, but as an incremental update it
can only jump versions 'in the correct order').
ntzrmtthihu777 said:
Barring actually getting the MSM I may have a method of recovery using fastboot and friends. However, I need the help of
a hotdogg owner with stock firmware & unlocked bootloader. The method is non-destructive (aside from the unlocking nuking
your data); just requires you to use fastboot to boot a twrp image and use adb to pull a partition (its 15gb, so to make it faster
you may want to use a real usb-c 3.0 cable; I don't think the orange one that comes with it is) and unpack it with a tool
called 'lpunpack' (unfortunately I don't know how to build it outside of an aosp/lineageos/grapheneos tree yet).
Click to expand...
Click to collapse
Getting my device tomorrow, but will obviously have to get it sim unlocked first, then wait the week for the OnePlus token to unlock the bootloader. But once I am at that point, I would happily do this if it could possibly lead to an alternate fastboot recovery method if no one is able to get the MSM tool. Obviously if anyone else can do this before I am able to, please do
ntzrmtthihu777 said:
Do you currently have one in an unflashed (to anything other than stock), unlocked state? If so I can probably guide you through how we can get a sort of
flashable stock image (flashed over fastboot). Hit me up if you are in that situation (sim unlocked, bootloader unlocked, and otherwise stock firmware).
Click to expand...
Click to collapse
I was wondering what particular device was mounted root, so I did: cat /proc/mounts
Apparently, / is /dev/block/dm-8
This is why TWRP is taking so long for Android 10: https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
"Android 10 also introduces a new dynamic partitioning system. Instead of having a dedicated system partition and a dedicated vendor partition, etc. Android 10 uses a super partition. I like to think of the super partition as a partition that contains a bunch of smaller partitions. One of the side effects of this dynamic partition system is that Google has chosen to use a form of the ext4 file system that is for all intents and purposes, read-only. This choice means that even if you wanted to, you can't easily mount and modify the system partition. We haven't really discussed this with other developers yet, but it may impact your ability to do things like install Gapps. In addition, the dynamic partition model means that eventually, we should probably provide you, the user, some GUI driven tools in TWRP to allow you to manage the dynamic partitions that are on the super partition." @Dees_Troy
jhofseth said:
I was wondering what particular device was mounted root, so I did: cat /proc/mounts
Apparently, / is /dev/block/dm-8
Click to expand...
Click to collapse
Yeah, but / is not terribly important compared to /system, /vendor, and /product (it is important tho)
jhofseth said:
This is why TWRP is taking so long for Android 10: https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Click to expand...
Click to collapse
Yeah, but twrp is not incredibly essential to the backup/restore process I've theorized about (still not sure about how it would work
in practice), just needed to get something to boot with root available without actually changing the stock firmware (by installing
magisk and such) in order to be able to pull the stock data.
---------- Post added at 12:38 PM ---------- Previous post was at 12:35 PM ----------
jhofseth said:
"Android 10 also introduces a new dynamic partitioning system. Instead of having a dedicated system partition and a dedicated vendor partition, etc. Android 10 uses a super partition. I like to think of the super partition as a partition that contains a bunch of smaller partitions. One of the side effects of this dynamic partition system is that Google has chosen to use a form of the ext4 file system that is for all intents and purposes, read-only. This choice means that even if you wanted to, you can't easily mount and modify the system partition. We haven't really discussed this with other developers yet, but it may impact your ability to do things like install Gapps. In addition, the dynamic partition model means that eventually, we should probably provide you, the user, some GUI driven tools in TWRP to allow you to manage the dynamic partitions that are on the super partition." @Dees_Troy
Click to expand...
Click to collapse
Yeah. This super partition is what I'm interested in. Once you copy it from the device (using adb pull /dev/block/.../super super.img)
you can extract it into its subpartitions using lpunpack. I believe one would be able to flash its subpartitions using fastboot in order
to recover from either a bad flash or a bad restore (like I and another user have, which left us on 10.0.13).
/dev/block/bootdevice/by-name/super
I made an image of super and file info reads 14.0 GiB (15,032,385,536).
That super.img compresses down to about 4.6 GiB in a regular zip file.
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
jhofseth said:
/dev/block/bootdevice/by-name/super
I made an image of super and file info reads 14.0 GiB (15,032,385,536).
That super.img compresses down to about 4.6 GiB in a regular zip file.
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
Click to expand...
Click to collapse
Nice, nice. Yeah. that's to be expected. I think with that file I and dandroid would be able to restore our phones, assuming
that's stock firmware. Potentially others. Do you have a reliable means to share the file, if you're willing to? Per the link you
posted it contains no userdata so it should be safe to share.
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