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
Related
Did my best to avoid having to ask for help, but looks like I've run out of ideas. I've got a 7840 that currently refuses to boot past the recovery screen, thanks (probably) to my own incompetence. Here's what happened along the way to this point:
First, probably important to note: my tablet is a Chinese-released 7840 running 5.0.2 Lollipop. The hardware is identical from what I can tell, but the software was definitely a bit tweaked as there were no Google services installed. (And sideloading any of the Google services always failed no matter how I went about it.) This is basically why I decided to start messing around with things.
Attempted to load the developer firmware. Wound up in the dreaded "Intel Inside" bootloop, but thanks to @xBIGREDDx and his unbrick.zip (http://forum.xda-developers.com/showpost.php?p=60663442&postcount=2) I was able to return to normal booting. No matter how many times I attempted to flash the open source firmware, I always got stuck in the bootloop and had to flash the unbrick.zip to be able to do anything. No ability to exit the bootloop in order to reach the bootloader meant this was a big impasse.
I then decided to use the tethered CWM method to root the device for the purposes of giving sideloading the Play Store another try. That worked just fine and I was able to root my 7840 without a hitch. I then created a nandroid backup (which suspiciously didn't generate an MD5 file) in case I managed to really screw things up trying to sideload the Google Services.
That's when I thought wiping and recovering the 4.4.4 Kit Kat nandroid backup might be a good idea. This of course didn't work, so I wiped and restored my own 5.0.2 backup. However, at this point things wouldn't boot no matter what I did. I would see the boot screen with the Dell logo and the Lollipop-style ANDROID text, but after a couple of minutes everything would reboot and after a couple of tries the device would boot to recovery and just sit.
After fiddling around with trying different restore methods, I decided to see if I could flash the developer firmware to no avail. (Unable to write to OSIP, security error, etc.) Then I gave @anggusss's 5.0.1 OTA update.zip a try. (http://forum.xda-developers.com/showpost.php?p=60632439&postcount=21) That gave me a different error:
"Can't install this package (Fri Apr 24 13:29:34 CST 2015) over newer build (Fri Apr 24 13:58:18 CST 2015)."
Frustrating to see that a build a half hour newer might be all I need. So, if any of you happen to have captured the 5.0.2 OTA build (or can help me tweak the 5.0.1 build to report itself as newer), would you mind giving me a hand? Would be most appreciative. I've written to Dell open-source support but don't expect to hear back for another week or so. It'd be nice to not be using the Venue as a paperweight for a week.
wirebook said:
No matter how many times I attempted to flash the open source firmware, I always got stuck in the bootloop and had to flash the unbrick.zip to be able to do anything. No ability to exit the bootloop in order to reach the bootloader meant this was a big impasse.
Click to expand...
Click to collapse
Out of interest, how was the tablet booted when you flashed the unbrick.zip (did you volup + power or just regular boot?) ?
Going back to the open-source firmware won't help, because they 4.x to 5.x transition included a re-partitioning, and the bootloader in the 4.x firmware doesn't understand the new partition scheme.
If you boot with the vol. down key held, do you get into fastboot mode? If you can, then you should be able to flash a system image and boot image. I have those pulled from my device; I can post them for you to try later tonight.
anggusss said:
Out of interest, how was the tablet booted when you flashed the unbrick.zip (did you volup + power or just regular boot?) ?
Click to expand...
Click to collapse
I've never gotten vol. up + power to do anything, is that normal? Only vol. down + power, and that'll get me into fastboot mode.
xBIGREDDx said:
Going back to the open-source firmware won't help, because they 4.x to 5.x transition included a re-partitioning, and the bootloader in the 4.x firmware doesn't understand the new partition scheme.
If you boot with the vol. down key held, do you get into fastboot mode? If you can, then you should be able to flash a system image and boot image. I have those pulled from my device; I can post them for you to try later tonight.
Click to expand...
Click to collapse
Ah, well this sounds like it's my problem, then. If you can get those images to me to try I'd be most appreciative! Should be able to give it a shot as I'm still able to get into fastboot.
wirebook said:
Ah, well this sounds like it's my problem, then. If you can get those images to me to try I'd be most appreciative! Should be able to give it a shot as I'm still able to get into fastboot.
Click to expand...
Click to collapse
system.img
This is inside a .zip file because I don't know how to get only the important bits, so I got the whole /system partition. Just unzip then 'fastboot flash system system.img'
boot.img
This is straight from the OTA zip.
You will be pre-rooted. Let me know if this goes well. :good:
xBIGREDDx said:
system.img
This is inside a .zip file because I don't know how to get only the important bits, so I got the whole /system partition. Just unzip then 'fastboot flash system system.img'
boot.img
This is straight from the OTA zip.
You will be pre-rooted. Let me know if this goes well. :good:
Click to expand...
Click to collapse
Thanks a lot for those! Flashed both boot and system, though the system gave me some sort of error on my machine ("Invalid sparse file format at header magi") and then continued to flash something ("sending sparse 'system'"). I saw the red text of some sort of error on the tablet but wasn't able to read it fast enough. The system flash did seem a bit suspiciously fast, though...
Anyway, now waiting to see if anything boots. Been sitting on the Dell/Powered By Android screen for a couple of minutes, though, so if nothing else it looks like I've at least found myself in a new place. Will try reflashing if no improvement and then get back with results!
Sorry if this is considered spamming my own thread, but didn't seem right to just edit my earlier post.
Couldn't get the system image to flash. First got the error about needing to flash as a sparse system, which seemed to be fine. But when the device tried to write the sparse chunk to the partition, it threw an error. ("remote: flash_cmds error!") Thought this might've been a bug of my particular version of adb/fastboot, but updating or trying a different version didn't work any better. In fact, things got worse as I can't even run fastboot on my machine (Windows) anymore without the program crashing on me.
Jumped over onto my Mac and things seemed to be going better, but no progress was made. Still threw that error whenever it came time to write that first sparse chunk. Might my partition table be totally out of whack? (If so, how do I go about fixing it without easy access to an adb shell?)
In other news, I realized the back of the tab has "Venue 8 784001" engraved on it, so there might be hardware / bootloader changes that I can't beat...
Well, I'm not 100% sure it's going to be able to flash the system.img correctly, I thought I could just pull it from my device and it would flash fine, but apparently not. It would be interesting to see what your partition table looks like, but I don't know of a way to get that without having a root shell.
If you have a hex editor or know how to use dd, try chopping off like 200 MB from the end of the image (I think it's all zeroes for at least that much) and see if it flashes then.
If you don't know how to do that, I could upload a modified image for you.
xBIGREDDx said:
Well, I'm not 100% sure it's going to be able to flash the system.img correctly, I thought I could just pull it from my device and it would flash fine, but apparently not. It would be interesting to see what your partition table looks like, but I don't know of a way to get that without having a root shell.
If you have a hex editor or know how to use dd, try chopping off like 200 MB from the end of the image (I think it's all zeroes for at least that much) and see if it flashes then.
If you don't know how to do that, I could upload a modified image for you.
Click to expand...
Click to collapse
wirebook said:
Sorry if this is considered spamming my own thread, but didn't seem right to just edit my earlier post.
Couldn't get the system image to flash. First got the error about needing to flash as a sparse system, which seemed to be fine. But when the device tried to write the sparse chunk to the partition, it threw an error. ("remote: flash_cmds error!") Thought this might've been a bug of my particular version of adb/fastboot, but updating or trying a different version didn't work any better. In fact, things got worse as I can't even run fastboot on my machine (Windows) anymore without the program crashing on me.
Jumped over onto my Mac and things seemed to be going better, but no progress was made. Still threw that error whenever it came time to write that first sparse chunk. Might my partition table be totally out of whack? (If so, how do I go about fixing it without easy access to an adb shell?)
In other news, I realized the back of the tab has "Venue 8 784001" engraved on it, so there might be hardware / bootloader changes that I can't beat...
Click to expand...
Click to collapse
When you dump an image is raw.ext4 it has to be converted to sparse image format for android 5.0.2
social-design-concepts said:
When you dump an image is raw.ext4 it has to be converted to sparse image format for android 5.0.2
Click to expand...
Click to collapse
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
xBIGREDDx said:
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
Click to expand...
Click to collapse
I think the image you passed me already employed some kind of compression on it, as I was getting errors about an invalid sparse data header or something like that. (The size on the disk was also less than the reported image size.) Unfortunately I'm unable to mount or convert it on any of my machines so I'm a bit useless.
Thanks everyone for all the help you've been, by the way!
wirebook said:
I think the image you passed me already employed some kind of compression on it, as I was getting errors about an invalid sparse data header or something like that. (The size on the disk was also less than the reported image size.) Unfortunately I'm unable to mount or convert it on any of my machines so I'm a bit useless.
Thanks everyone for all the help you've been, by the way!
Click to expand...
Click to collapse
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
If you want to try re-partitioning (could be dangerous, could be harmless), try these commands with the partition file from the OTA package:
EDIT: For anyone else coming along, don't do this, it didn't work out well for wirebrook. /EDIT
Code:
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl kk2lp_partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot oem stop_partitioning
You may also want to erase data while you're in there.
xBIGREDDx said:
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
Click to expand...
Click to collapse
That must be what's happening. I'll fiddle with things a bit more later on. It's a bummer there aren't any custom ROMs I could simply flash as an alternative to getting stock up and running...
xBIGREDDx said:
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
Click to expand...
Click to collapse
xBIGREDDx said:
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
Click to expand...
Click to collapse
It's looking for the sparse magic header that's not there I can when I get home you could also try to use 7zip to compress it to a .gz but I believe Intel stopped support for that format in 4.4.4.
I'm at work I have it at home if your on Linux and want to convert it.
social-design-concepts said:
It's looking for the sparse magic header that's not there I can when I get home you could also try to use 7zip to compress it to a .gz but I believe Intel stopped support for that format in 4.4.4.
I'm at work I have it at home if your on Linux and want to convert it.
Click to expand...
Click to collapse
Not sure this'll be useful for me any more because... (see below)
xBIGREDDx said:
If you want to try re-partitioning (could be dangerous, could be harmless), try these commands with the partition file from the OTA package:
Code:
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl kk2lp_partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot oem stop_partitioning
You may also want to erase data while you're in there.
Click to expand...
Click to collapse
Gave this a shot and partitioning seemed to work just fine. Flashing the OTA boot.img worked just fine, and attempting to flash your system.img once again threw an error at me. Thought I'd perform a reboot at this point (bad idea!) to see what I was working with and then I found myself with @anggusss' USB screen. (http://forum.xda-developers.com/showpost.php?p=60675581&postcount=5) Probably should've tried flashing a something else just to see if that did anything.
Guessing I've now got a brick, because I'm no longer able to get it to register with Fastboot. I can, however, flash the open-source firmware and the unbrick.zip firmware, which reacts exactly like when @anggusss did it. We'll have to see if Dell ever gets back to my original query for help, otherwise might have to look into contacting Dell for a replacement.
You might have better luck, just using one of the tethered TWRP recoveries, If someone with a working system backups up system via TWRP recovery and shares it you could use the TWRP recovery to restore it.
I have Linux version tethered TWRP up and SDC has Windows version of tethered TWRP up.
Linux version
http://forum.xda-developers.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075
Windows Version
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
vampirefo said:
You might have better luck, just using one of the tethered TWRP recoveries, If someone with a working system backups up system via TWRP recovery and shares it you could use the TWRP recovery to restore it.
I have Linux version tethered TWRP up and SDC has Windows version of tethered TWRP up.
Linux version
http://forum.xda-developers.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075
Windows Version
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Click to expand...
Click to collapse
Thanks for the thought, but if I can't get into Fastboot mode (or get the computer to recognize the device as being in Fastboot mode)... kinda unable to use it.
wirebook said:
Gave this a shot and partitioning seemed to work just fine. Flashing the OTA boot.img worked just fine, and attempting to flash your system.img once again threw an error at me. Thought I'd perform a reboot at this point (bad idea!) to see what I was working with and then I found myself with @anggusss' USB screen. (http://forum.xda-developers.com/showpost.php?p=60675581&postcount=5) Probably should've tried flashing a something else just to see if that did anything.
Guessing I've now got a brick, because I'm no longer able to get it to register with Fastboot. I can, however, flash the open-source firmware and the unbrick.zip firmware, which reacts exactly like when @anggusss did it. We'll have to see if Dell ever gets back to my original query for help, otherwise might have to look into contacting Dell for a replacement.
Click to expand...
Click to collapse
Oh man, sad to hear, I've done that successfully in the past, they must have changed something in the process. I check just about every day for an update to the dev. firmware. Last time around it took them just over two months from release, so maybe, end of June?
xBIGREDDx said:
Oh man, sad to hear, I've done that successfully in the past, they must have changed something in the process. I check just about every day for an update to the dev. firmware. Last time around it took them just over two months from release, so maybe, end of June?
Click to expand...
Click to collapse
Fingers shall stay crossed till the end of the month, then! Contacted Dell Support and- just as I predicted- they don't want to help out. Something about being unable to do anything at all for Dell products purchased outside of their support areas (US and Canada). What a joy of a phone call that was...
An internet search landed me on guides for unbricking the Asus Zenfone displaying a similar USB symbol. They used the xFSTK Downloader to flash a set of files which then gave them renewed access to the bootloader (and thus fastboot). Played around with the xFSTK-Downloader and Manufacturing Flash Tool apps and can see the 7840 and even flash the (open-source and unbrick.zip) firmware, however I'm at a loss for what I might use for the Operating System flash files. Anybody have any thoughts?
Feel like I'm so close to getting this thing unbricked. If I could just figure out where to find the .bin "OS Image" that the tool wants...
Edit: Would also need the droidboot binary. FIngers crossed for Dell to release all of this soon...
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
**Edit: Be sure to read comments at the end of this post******
I've already posted this a few times but I figured I would try to save some people time who want/need to root from any security patch. This is a copy and paste from an answer I gave in another thread but it's a basic how to.
Install DSU sideloader app from playstore to boot a prerooted GSI then use Partitions Backup and Restore app from playstore to save copies on your device. Install magisk app and patch the extracted boot.img and then transfer backups along with the patched boot image to your PC for safekeeping and flash the patched boot.img in fastboot. You can rename any .bin files to .img to flash them if they get extracted as a .bin file. Check your settings in the partitions Backup and Restore app before starting the backup process. You can choose to save them in an easy to find directory and for me it was better to choose to save them RAW/uncompressed then just compress them all into a single archive rather than having a hundred separate archives for each individual partition because it makes it easier if you have to reflash things if you need to recover. You may want to disable battery optimization for the app because it takes a while to extract all the images doing a full backup but its well worth the wait time if it saves you from a brick later on.
I wish I had time to elaborate but hopefully someone else can take the time to elaborate and add to this for anyone needing step by step. I'm surprised nobody has done this already.
Credits to AndyYan for giving advice on the root method. I stole this from him and just made a post with a title that makes it easier to find since so many are still asking how to go about rooting their devices.
*****REQUEST TO COMMUNITY********
There are many who are already on August Security patch and i dont have time to update and post the newest images. So if you are on august patch and pull backups I ask that someone please be so kind as to upload a copy of your backup to Google Drive or a filehosting server of choice and post a new thread so that others can unbrick their devices.
*Please ***DO NOT include**** the following partitions*:
DEVINFO
DINFO
FRP
KEYMASTER_A
KEYMASTER_B
KEYSTORE
LOGDUMP
***MDM1M9KEFS1
***MDM1M9KEFS2
***MDM1M9KEFS3
***MDM1M9KEFS4
MODEMDUMP
OPLUS_SEC_A
OPLUS_SEC_B
RAWDUMP
SECDATA
STORSEC
USERDATA
VM-KEYSTORE
*** These partitions may/contain YOUR personal device info, DO NOT make these public***
You can make a new Google account for the sole purpose of uploading these for the community so as not to fill your own GDrive. Be sure to change permissions for the images to share with anyone who has the link. This would be very much appreciated by many.
*****Update 09/18/2022*****
Thanks to ctschrodinger88 & dmtec for posting more detailed instructions!!! you can find ctschrodinger88's instructions below, scroll down to the 5th post.
dmtec also posted instructions in another thread linked here: https://forum.xda-developers.com/t/august-boot-img.4491831/post-87426877
we are still in need of august modems if anyone cares to upload them to their drive and link them or any other filehosting service.
can you suggest me a pre rooted gsi rom please?
thanks
fictisio said:
can you suggest me a pre rooted gsi rom please?
thanks
Click to expand...
Click to collapse
i used crdroid but its buggy, launcher crashes but its useable, atleast to get this done and then be sure to discard it in the DSU sideloader notification when you reboot so the inactive slot is empty, it will make for easier updates/mods later
has anyone had luck flashing the file in this article? https://www.getdroidtips.com/oneplus-nord-2t-5g-firmware-flash-file-2/#google_vignette
I used the info provided and referenced here as a guide and some external pieces and have things working.
I'll caveat the following, I don't remember the current firmware version I started with, but I'll try to remember to update.
I have the Nord N20 5g, but not the T-mo branded one, though in looking at this, the concepts should be the same.
Base assumptions:
- If you haven't done these beforehand, stop and take care of it. Research if you need, but please DO NOT just keep going or copy, paste, and run, without understanding to some extent what you're doing. If you just run commands it can be much harder to fix later.
a. Your phones bootloader is unlocked. (If you haven't already done it, when you do, your data will be gone, so if you care, back it up NOW)
b. You have access to an Android terminal of some sort (adb or on-device terminal) and you know how to use it. Unless you absolutely can't use a computer for some reason, I would use adb, it makes data backup easier (IMO).
c. You have somewhere to store your backed up partitions (THIS IS IMPORTANT)
Step 0: Download a pre-rooted Generic System Image (GSI) to use. Put it in a good working directory. This page links to several. https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
I used the LineageOS image by @AndyYan
If you are wondering about the various file endings this is the basic version
Code:
<ARCH>_xyZ
<ARCH> can either be arm, a64 (arm32_binder64) or arm64
x can either be a or b
y can either be v, o, g or f
Z can be N or S
b = a/b
a = a-only
g = gapps
o = gapps-go
v = vanilla (no gapps included)
f = floss (free & open source apps instead gapps)
N = no superuser
S = superuser included
From: https://forum.xda-developers.com/t/teclast-t30-t1px-suitable-gsi-roms.4211427/
Step 1: Enable the Dynamic System Update (DSU) feature flag, you can follow the exact steps for this in this section https://developer.android.com/topic/dsu#feature-flag
If you are unsure, just run the `adb shell` command.
Step 2:
If the image you downloaded needs to be in ".gz" format. Some of the tools will handle alternate types, but that's because it rebundles it at ".gz", you can save some effort doing it yourself.
Code:
gzip -c [IMG_NAME]..img> [IMG_NAME].gz
Step 3: Push the image to the device
`adb push [IMG_NAME].gz /storage/emulated/0/`
This is where I switched from ADB to on-the-device.
Step 4: Download the DSU Sideloader: https://github.com/VegaBobo/DSU-Sideloader
You can do this with adb but I wasn't able to get it to run, so I went with the DSU Sideloader app above which made it much simpler.
Step 5: Run DSU Sideloader. You can follow the instruction there in the README. You will need to run a command that the app provides, either via adb or an emulator. Then you will reboot via the notification.
Step 6: [Once you reboot] Enable Developer tools in phone settings.
Step 7: BACKUP, BACKUP, BACKUP (Please do this now. It will help make life much, much better if you ever have an issue and need to reset.)
This was my process:
Bash:
adb shell
su
mkdir /sdcard/partitions
cd /dev/block/by-name/
for x in *; do dd if=/dev/block/by-name/$x of=/sdcard/partitions/$x ; done
# Note the collective size will be greater than the default space on the GSI boot, so you will want to separate things
# Back on local machine
mkdir [working_dir]
cd [working_dir]
adb pull /sdcard/partitions
# Your files from the adb command should populate the folder
mv [working_dir]/partitions/* [working_dir]/
# On device
rm /sdcard/partitions/*
# repeat the commands above as often as needed.
I don't know for sure all the files you will want to backup, but I pulled everything just to be safe. Keep them safe, because it is your safety net if you fall.
Step 8: Get boot_a or boot_b back on the device along with Magisk.apk (Please only download from here: https://github.com/topjohnwu/Magisk/releases)
Step 9: Install Magisk.apk (you can do this via
Code:
adb install ./magisk.apk
)
Step 10: Launch Magisk and install it to the book image stored on your sdcard.
Step 11: Pull the patched image to your local machine.
Code:
adb pull /sdcard/Download/magisk_patched-[stuff].img
Step 12: Boot phone to fastboot
Code:
adb reboot bootloader
Step 13: This is where there is an ideal and a real.
Ideal command
Code:
fastboot boot magisk_patched.img
where fastboot transfers the files and things just work, and if you reboot the system the regular boot.img is used. I haven't been able to get that to with this device.
I instead just ran
Code:
fastboot flash boot magisk_patched.img
which replaced the existing boot image, which is good, if it works, but if it doesn't, this is why you have backups!!!! Reboot the phone.
Step 14: When you boot, finish installing Magisk and you'll be ready to go.
If I remember other steps I'll add, or if you have questions I will try to help answer.
I just got a MetroPCS nord n20 (gn2200) and will try to root in the next couple days.
ScarletWizard said:
n20
Click to expand...
Click to collapse
Have they removed the unlock portal?
Damn, it's been a long time. Glad to be back.
ScarletWizard said:
No. My serial is 7 digits
Click to expand...
Click to collapse
seems to be a common defect.... if ur device is paid off oneplus can generate you a token but it takes weeks of back-and-forth with support to get it escalated...tmobile may or may not allow you to do that on a device that isnt paid off but i wouldnt even ask tmobile about it if your not paid off already, will only make it harder for those who are trying to unlock theirs if it IS the case that tmobile doesnt want you to unlock it until youve paid the device off in full....oneplus will probably uphold tmobiles decision if your device isnt paid off. for now, we are able to unlock tmobile devices through the portal regardless of the financial status of the device. though you will still be SIM locked unless tmobile unlocks that for you. and their definitely NOT gonna do THAT til it gets paid off.
U.S. carriers dont like customers having unlocked devices and is against most user-agreement policies and can get your service terminated leaving you owing for a device you cant use and for the price of the contract you were on for service
your device is a CPH2459 and not a GN2200?
fictisio said:
can you suggest me a pre rooted gsi rom please?
thanks
Click to expand...
Click to collapse
Andy Yan's Lineage18 or 19..
DrScrad said:
Andy Yan's Lineage18 or 19..
Click to expand...
Click to collapse
pixel experience, crdroid... havent gotten kaleidoscope to work yet. Have heard that someone got aosp a13 going.... There are so many and so long as u use a matching security patch ur good. might work with a newer patch but of the ones ive tried i got thw matching patches to work. If you find one thats on a newer patch in the gsi page you should be able to follow the link and find an older release to match the patch ur on. If ur on may patch try to find a may patch just to make it pess likepy that there will be priblems. If on july or august, likewise find july or august sec patch release. newer patched systems MIGHT work with ur older patched bootloader and other partitions(modems etc...) but def would not advise just straight flashing mismatching security patches... Best to sideload first and see if u can get it working first. Its not very simple to dual boot these devices but i think someone did some work and posted a work around for doing that on a/b devices somewhere on xda......
Am willing to share my stock image with anyone willing to help. I am on the September security update on a OnePlus Nord N20 5G unlocked (Non-Carrier). I am running version 11 and android security update 2022-09-05.
I am having real issues getting LineageOS through DSU. It fails immediately on start every time. Bootloader is unlocked, it even shows through fastboot (Secure boot = on though), flag is set per instructions, and I am trying to install lineage-19.1-20221011-UNOFFICIAL-arm64_bvS.gz . I tried two different versions of the DSU app but nada.
oromis995 said:
Am willing to share my stock image with anyone willing to help. I am on the September security update on a OnePlus Nord N20 5G unlocked (Non-Carrier). I am running version 11 and android security update 2022-09-05.
I am having real issues getting LineageOS through DSU. It fails immediately on start every time. Bootloader is unlocked, it even shows through fastboot (Secure boot = on though), flag is set per instructions, and I am trying to install lineage-19.1-20221011-UNOFFICIAL-arm64_bvS.gz . I tried two different versions of the DSU app but nada.
Click to expand...
Click to collapse
make sure u r using a lineage version with the same security patch as your current OS if your on September u need a GSI on september. i personally gave up on lineage after trying a couple but was successful with a few others while dsu sideloader still worked for me, im not sure what i did to break it on my devices but i havent been able to get it to work on either device in a while.
i have yet to try the october firmware but it should be easy to downgrade and root if you think its the new updates. although make sure ur disabling verity. u might wanna disable the checks on vbmeta_boot too... i usually just disable it on all 3 vbmeta's to be safe.... i have a full july dump and someone else has posted the august dump on TG but that doesnt help in your case since you have the CPH2459 and we are on GN2200's nobody has been able to successfully crossflash them yet and im not sure if it will be possible or not but everyone that has tried it has bricked their devices so far. most have gotten them running again but have lost fingerprint
ScarletWizard said:
im on gn2200
Click to expand...
Click to collapse
Ok my last upload didn't upload correctly for some reason. I will re upload tomorrow I think..... I need to figure out exactly which partitions are device-specific.... I know which partitions get updated in the incrementals so if all of them don't get flashed then everything won't match but I have a feeling that the incrementals update a device-specific partition or two and if so then u will lose fingerprint at minimum...... I think I should just pull full backup of all partitions and then go for it. Worst case so long as u do everything right. U just don't boot and have to reflash the stock boot image... Be sure to flash the stock image to both slots just in case and then switch back to ur active slot and flash the patched boot image. I mean if it was me I would b comfortable doing it but that's completely ur call, I don't wanna encourage anything because there ALWAYS a risk something could go wrong. Power outage or something and it's screwed up but any time u r flashing u will always be taking a risk. Though I think the risk is minimal so long as u do everything right and there's not much to the simple root process, patch the boot image and flash, if it doesn't work then reflash the stock one. If it DIES work out for u we would b grateful for the October firmware if u wanna share it, we didn't get October yet.
ScarletWizard said:
If it dies. Lol scary.
I'm in the process of doing the partition thing
Click to expand...
Click to collapse
If it DOES.. Sry
ScarletWizard said:
who is the ADMIN of this n20 thread?
Click to expand...
Click to collapse
Just look.for the moderator edits lol
PsYk0n4uT said:
seems to be a common defect.... if ur device is paid off oneplus can generate you a token but it takes weeks of back-and-forth with support to get it escalated...tmobile may or may not allow you to do that on a device that isnt paid off but i wouldnt even ask tmobile about it if your not paid off already, will only make it harder for those who are trying to unlock theirs if it IS the case that tmobile doesnt want you to unlock it until youve paid the device off in full....oneplus will probably uphold tmobiles decision if your device isnt paid off. for now, we are able to unlock tmobile devices through the portal regardless of the financial status of the device. though you will still be SIM locked unless tmobile unlocks that for you. and their definitely NOT gonna do THAT til it gets paid off.
U.S. carriers dont like customers having unlocked devices and is against most user-agreement policies and can get your service terminated leaving you owing for a device you cant use and for the price of the contract you were on for service
Click to expand...
Click to collapse
One small problem, although Metron PCS uses T-Mobile towers, they are their own entity and T-Mobile does not have their Bootloader codes. Only OnePlus and Metro PCS have the Metro PCS unlock.bin file. That's what I came here was to try and find a dedicated metro bootloader unlock web page. Like the T-Mobile dedicated page. There is not one so it's going too take several calls over several weeks unless some one here knows a different way or a link to a metro PCS bootloader unlock page? Anyone chime in on this and save all of us that are running in circles back down the straight path to an unlocked bootloader..
jayram1408 said:
One small problem, although Metron PCS uses T-Mobile towers, they are their own entity and T-Mobile does not have their Bootloader codes. Only OnePlus and Metro PCS have the Metro PCS unlock.bin file. That's what I came here was to try and find a dedicated metro bootloader unlock web page. Like the T-Mobile dedicated page. There is not one so it's going too take several calls over several weeks unless some one here knows a different way or a link to a metro PCS bootloader unlock page? Anyone chime in on this and save all of us that are running in circles back down the straight path to an unlocked bootloader..
Click to expand...
Click to collapse
I'm about to file a FCC complaint to get mine then.
in this thread i am going to outline the method i used to restore my device to may security patch after completely botching my current install after trying to root, on august security patch.
a major hand to PsYk0n4uT for the suggestions he's posted in response to my problems, giving me the ability to figure out what's really going on here amongst other things.
(this is compatible with metropcs branded devices, therefore is compatible with t-mobile branded devices and so on)
anyways.
download this may OTA i discovered somewhere online. (hint: if download quota is exceeded. make a copy to your gdrive, then put it in a folder. download the folder and you will bypass the quota)
the OTA will contain msmdownloadtool, but it is unusable in it's current form because it's an internal tool. you're gonna want to download this tool off github to help assist in decrypting the .ofp file and flashing it's complete contents over automatically.
extract the OTA zip, and place the tool from github in the same folder. if using linux, install the python requirements and if you're on windows, i would suggest replacing the adb/fastboot executables with current versions. probably shouldn't matter, but i did in this case.
put your phone into fastboot and run the tool. further instructions depending on OS, are on the repository's page.
after flashing i had to switch my active slot over to the prior inactive slot before i could boot.
now that you've got your device downgraded, get through the initial setup, set it up offline, and put your phone into power saving mode so it can't automatically update (just in case)
instead of using DSU sideloader to extract the files we need, we can use the same .ofp file that our images came from and extract its contents with this tool
install magisk, copy your boot image over, patch the boot image, return it back to your computer, and enter fastboot mode.
proceed to flash the boot image, and all 3 vbmeta images. (important: be sure to disable verification and disable verity when flashing your vbmetas)
???
profit
i hope this can help anyone that's got a paperweight for a device at the moment, and help anyone who wants to root their device without a bunch of possible nonsense. in turn, hoping this can accelerate any possible development with this device.
protip: after getting everything installed and set up, install the systemless debloater module in magisk and download de-bloater from f-droid. "remove" the update service application (com.oplus.romupdate) and the software update tab in settings will now think you're on the latest security patch and will prevent your device from accidentally being updated. unless you want that to happen.
mirrors:
[vngsm.vn] GN2200export_11_A.05_2022050718170202.zip | VietNam GSM Services
vngsmservices.com
OnePlus Nord N20 5G Flash File (Official Firmware) GSMMAFIA
OnePlus Nord N20 5G Qualcomm Snapdragon 695 5G Flash File available here with MSM download tool to download via Direct link.
www.gsmmafia.com
And no problem man. Im glad others are sharing their knowledge and experience here. I've been focused on other things trying to make some progress on the device but still having to learn a lot along the way.
Hopefully we will have custom recovery soon. Looking promising so far and the real devs have given more time than I could possibly ever expect towards a device they don't even own.
For anyone wanting to know more about the people that are doing the leg work check out the team at https://t.me/Android_General_Chat The devs work hard to make these things happen so if you wanna help the cause consider making a contribution to them.
dmtec said:
in this thread i am going to outline the method i used to restore my device to may security patch after completely botching my current install after trying to root, on august security patch.
a major hand to PsYk0n4uT for the suggestions he's posted in response to my problems, giving me the ability to figure out what's really going on here amongst other things.
oneplus seems to be weakly supporting this device because i tried to ask them again for the OTA (i mean, it's pulling from somewhere, right) and they told me that i'd need to send it into a service center for repair. what's the point of unlockable bootloaders if user error can't be corrected in some way.
(this is compatible with metropcs branded devices, therefore is compatible with t-mobile branded devices and so on)
anyways.
download this may OTA i discovered somewhere online. (hint: if download quota is exceeded. make a copy to your gdrive, then put it in a folder. download the folder and you will bypass the quota)
the OTA will contain msmdownloadtool, but it is unusable in it's current form because it's an internal tool. you're gonna want to download this tool off github to help assist in decrypting the .ofp file and flashing it's complete contents over automatically.
extract the OTA zip, and place the tool from github in the same folder. if using linux, install the python requirements and if you're on windows, i would suggest replacing the adb/fastboot executables with current versions. probably shouldn't matter, but i did in this case.
put your phone into fastboot and run the tool. further instructions depending on OS, are on the repository's page.
after flashing i had to switch my active slot over to the prior inactive slot before i could boot.
now that you've got your device downgraded, get through the initial setup, set it up offline, and put your phone into power saving mode so it can't automatically update (just in case)
instead of using DSU sideloader to extract the files we need, we can use the same .ofp file that our images came from and extract its contents with this tool
install magisk, copy your boot image over, patch the boot image, return it back to your computer, and enter fastboot mode.
proceed to flash the boot image, and all 3 vbmeta images. (important: be sure to disable verification and disable verity when flashing your vbmetas)
???
profit
i hope this can help anyone that's got a paperweight for a device at the moment, and help anyone who wants to root their device without a bunch of possible nonsense. in turn, hoping this can accelerate any possible development with this device.
protip: after getting everything installed and set up, install the systemless debloater module in magisk and download de-bloater from f-droid. "remove" the update service application (com.oplus.romupdate) and the software update tab in settings will now think you're on the latest security patch and will prevent your device from accidentally being updated. unless you want that to happen.
Click to expand...
Click to collapse
BROOOO you are EFFING AWESOME! MUCH LOVE!
bumping my own thread because people are being real extra after "bricking" their phones trying to get them working again
Really glad people are still working on this device. I've been away for a while and no longer have access to mine right now so just wanted to say thanks to those of you continuing the efforts
Careful with this. Windows Defender flagged a virus when I tried to download it.
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