I need an Odin expert, that knows how to..... - Android Q&A, Help & Troubleshooting

....... create an ODIN flash file from .img files........ I know there are numerous threads regarding this topic but having never done it before I'd think a little help would be wise (for the actual process).
Too this end, I've zipped up three files; system.img recovery.img and boot.img. They are for a Samsung device and are known good files. I can not fastboot flash them; my fast boot is broken (don't ask). However, Odin connects perfectly to my PC (with the device in download mode, of course .
If someone could either do the actual conversion, or point me to a procedure that ACTUALLY works, I'd be most appreciative. I'd upload the files here, but they're too big. If you want to try and help me do this, I could easily email the zip file to you, however.
BTW, I'm able to examine the contents of system.img with ex2explore.exe, but not the other two files. I assume they are not the same format??
And, yes (if it makes any difference) my boot loader is unlocked. Thanks, everyone.
Boowho??

Related

[Q] Getting SGS2 back to stock (Optus) - Help!

Hi guys.
My phone has been having major signal issues, no signal or emergency calls only next to an exact same phone that has no problem. Talking to my provider, it appears to be the phone and I need to send it back for repair. Problem is, I have a different firmware on there. I obviously need to get it back to the stock optus rom it came with. I know computers and stuff, but im a bit lost in this area. I've done a lot of searching on here but can't seem to find a specific resolve to this issue.
I'll try and sum it up.
Currently running Litening Rom 5, which i flashed with odin. I found on here the link for the original optus branded rom (GT-I9100_OPS_I9100XWKE7_I9100XXKE4_I9100OPSKE4) but after downloading it I'm more lost. The 7zip file had the following files in it:
boot.bin, cache.img, factoryfs.img, hidden.img, modem.bin, param.lfs, sbl.bin and zimage.
I have no idea what to do with these. I've also read that CWM is another possible way to do all this. My rom has it so that might be possible. I'm not fussed about keeping any files, I was gonna do a factory reset before I send it away anyway. I wanna completely wipe my phone and get it back to exactly how it was, so when optus look at it, its how they sent it to me, especially with no yellow triangle on boot.
What should I do with these files? The other option I have is if I can get the rom dumped off a friends optus phone and simply put it onto mine. I know 2 friends with them, can I plug their phone into my PC and use the dump button in odin, or will I get the same files?
Other question I have are:
1) Will Optus know what version of the firmware came on the phone (XXKE7 or whatever) and therefore realise a possible older version is on there, causing suspicion?
2) Is it possible that custom firmwares can screw up my reception? Friends are running stock and they have no issue, though saying that, its still not as good signal as a Nokia.
If you've read this far, thank you very much, I really appreciate it. I'm just so lost, freaking out a bit, going a bit insane with the phone constantly not having signal and just low on time to sort it out. Any help would be appreciated. Thank you!
Hi.
First off, if you're already down to the .bin and .img files, you extracted too much.
The archive you downloaded should contain a .tar file - DO NOT extract this one! You need the .tar as .tar.
Then download an App called "Odin" (likely to be found in the very same thread where you found the firmware) and use that one to flash the .tar onto the phone.
Instructions for that are also in the thread where you found the firmware.
That should already solve most of your hazzle.
If I'm not mistaken, flashing your phone's kernel would case
Cause the binary flash counter to clock. And the phone does keep a record of how many custom kernels you have been through. So I would say if they wanted to know, they would be able to find out.
In that case, spend the 5 to 10 bucks on eBay for the USB jig that resets the counter.
I have one too, "works nicely" is an understatement
HellcatDroid:
The one file I downloaded was a 7zip compressed exe. When I extracted that, I got the listed files, there was never a .tar file.
I had no idea about the kernel flash counter, but it sounds like it could be an issue. I saw those USB jigs, but though they were just a way to get into downloading mode if you'd somehow screwed up the normal way. Is that all they do, or much more?
TroyX87 said:
HellcatDroid:
The one file I downloaded was a 7zip compressed exe. When I extracted that, I got the listed files, there was never a .tar file.
Click to expand...
Click to collapse
You're doing it wrong.
Intratech said:
You're doing it wrong.
Click to expand...
Click to collapse
You know what would be awesome? If you explained why. I have no idea why I'm doing it wrong. Did I download the wrong file? (didn't have many options). Or would it be better to get a dump from a friends phone that has the desired rom/kernel?
How do I know why you're doing it wrong? The files are self extracting, all you need to do is double click it and point to when you want the included tarball extracted. You will then have a single tarball which includes everything in a single package. This has all been covered in the tutorial.
The file was a compressed exe, I dont think loading it on as a rom would have worked. Though when I extracted that (self extracting exe), I ended up with all the seperate files, there was never a .tar.
Is it safe to simply put those files into a .tar file with winrar? Is that all it is? Or will I risk bricking my phone? I had a look in the tutorials but couldn't see anything about it.
Thanks
TroyX87 said:
The file was a compressed exe, I dont think loading it on as a rom would have worked. Though when I extracted that (self extracting exe), I ended up with all the seperate files, there was never a .tar.
Is it safe to simply put those files into a .tar file with winrar? Is that all it is? Or will I risk bricking my phone? I had a look in the tutorials but couldn't see anything about it.
Thanks
Click to expand...
Click to collapse
Where did you get the file from? Optus firmwares are in the carrier branded firmware thread in the dev forum so you can download a copy from there.
I grabbed the exe from your other thread, it had 5 different links and only 1 worked at the time.
But you know the worst part? I just figured it out. The exe extracted a .tar file, but in my rushing and stressed-ness, i didn't realise that was the one, it was a winrar file so i just thought it was compressed or something, like a zip.
My bad. I wont be flashing just yet, gonna replace my sim card first. I got used to the idea of wiping my phone and starting again, but now I realised how annoying that would be. Bought a USB jig too, just in case.
Appreciate your help, sorrying for being a n00b!

[HOWTO][MINI][ST15i] Restore Stock ROM from Cyanogen and other ROMs

I was very disappointed in Cyanogenmod. Although awesome it was with all those features, it was riddled by bugs and stability issues. I slowly realized the hard way that the Xperia Mini is not a very popular phone, so any bugs on it will take time to be fixed. In some cases, maybe not at all. So I'm sticking to rooting my phone with the stock ROM, and will try the official ICS when it comes out. It took me a lot of time to understand how to go about doing these things, around 3 whole days just to get Cyanogen on. And then bombarded with these issues. I had issues after issue, and finally called it quits and returned to stock ROM.
Don't get me wrong, I'm not saying that Cyanogen is a worthless ROM. Infact, the devs did a stupendous job on it, but somehow it still isn't usable for me for everyday purposes. Atleast, not without slowing me down.
So I wrote this so people could be spared of the hassle non-geeks like me would go through. Hopefully this is easy to understand and works well for you. None of this my own- this is information I gathered from many different posts and threads into one easy to follow guide. I do not take credit for any of this (other than converging it altogether here).
GUIDE : To return to stock ROM, use this Flashtool method. I'm assuming you are aware of fastboot as well ( You had to do that while trying to get Cyanogen on). So anyways-
1) Download Flashtool from here
http://androxyde.github.com/Flashtool/
I recommend grabbing the zip instead of the installer and unzip to the root of C: drive. (C:\Flashtool\)
2) Get the Xperia Mini stock ROM ftf file from here
http://www.multiupload.com/DAVR31YISS
3) Copy the FTF file and go to the Flashtool folder you extracted. Paste it inside the 'firmwares' folder.
4) Launch the software and click the 'Flash' button (the button with the lightning icon.). Select the 'Flashmode' option. If you did like I explained the software will have already found the FTF file, and all you have to do is click OK. Else browse for the file and click OK.
5) Follow the instructions that shows on the software. Note that the service button for our phone is the 'Volume Down' key. Use that.
Voila! You will now have returned to Stock firmware. But you still have to do certain things to make the phone completely functional (some things like Wifi, haptic feedback and all dont work when you flash this way).
1) First, root the phone. Use DoomLords method, easiest way.
http://forum.xda-developers.com/show....php?t=1321582
2) After you've done that, switch off the phone. Connect the phone so the fastboot can work (Switch off, connect using the Volume Up key. The blue LED light on top will confirm you've connected that way)
3) Remember that FTF file you downloaded? Go to that file, change the extention from 'ST15i_4.0.1.A.0.283_(1249-8388).ftf' to 'ST15i_4.0.1.A.0.283_(1249-8388).rar' (RAR in the end). Unzip it. Copy the 'kernel.sin' file.
4) When you setup fastboot previously (while installing Cyanogen), you would've installed Android SDK and some other stuff. Go to the android-sdk folder, navigate to 'tools' and paste the 'kernel.sin' file inside that folder.
(If you want to learn more about setting up fastboot, look here.)
5) Open command prompt (Cmd.exe). Change the directory to tools inside the android-sdk folder.
For example, in my case it would be
cd C:\android-sdk-windows\tools
Type in
fastboot flash boot kernel.sin
There! Now Wifi, Market and anything else that wasn't working before should be working now.
If you have any issues, reply to this thread. I'll try to assist if I can.
Cheers.
All good
I just wanna say thx I was on cyanogen and the SE software updater wasn't restoring the stock rom, I downloaded the .zip and change it to .ftf then flashed it with flash tool and that's it all working and I guess that when I did flash the stock rom also flashed the stock kernel but I'm just guessing, anyway thanks a lot.
broken link
Hi,
i have tried to follow your steps, but unfortunately the link to the stock ROM seems to be broken:.
could you please upload the file somewhere else?
thanks
2cent2
help !
Im geting this error "processing of loader
.sin finished with errors" what should i do?

[Q] Downloading and Flashing Entire ROM via SP Flash Tool

Hello!
I need some help and I know this is the place to find it!
I have searched for several days all over the internet trying to read and gather information, and I am coming up short.
I know Bruno Martins has posted some information on his blog on how to "readback" (backup) your current rom for your phone, but there is no information on how to flash the entire ROM package back to your phone (at least with regard to the errors you may receive).
Basically, I am looking for some help on how to backup one of my phones entire rom package and put it on my other phone that I messed up via the Smart Phone Flash Tool (the exact same model: Star Touch Diamond 2 B2000 MT6573).
The new phone works perfect, I have never touched it, my old phone which is the same model I deleted and formatted the system so I need to put the stock rom on.
I was able to do a "backup" of my new phone, but when i try to flash the preloader and uboot, etc, the sp flash tool says error loading file, or region too large with overlap.
Any help would be greatly appreciated!
By the way, my phone is not bricked, but I cannot access recovery! I was able to find and install another fully assembled rom to my phone and the phone does power on with lights, but it doesnt have the display driver I need so I cannot see anything.
The reason I flashed another rom was because the phone was essentially bricked and wouldnt do anything, and that was the only rom I could find on the internet that was a full package (preloader, uboot, system, etc) but isnt compatible with phone.
Anyhow, if I understand correctly I need to use hexadecimal calculator to find length of partitions of original phones rom, readback the files, somehow edit the preloader file? then flash them back to the old phone?
Please help!
I would love to make a tutorial of this method with pictures and possible errors for everyone if we could get this solved!
Please point me in the right direction!
And I wanted to thank BRUNO in advance for his hard work and help!!
have you tried the neutrino rom from notorious? its reallllly small around 50mb. you may be able to install that since it so small, then work your way back down? not too sure and i can say im no grandmaster but it might work!
***derp. neutrino... thats for atrix only. but hey same concept. maybe a small barebones rom will get you running enough to get things done properly.
Hello stokemonkey!
No, I have not tried the neutrino rom. My main goal is to take my working phone and copy the firmware to my other phone which is the same model. I attempted to flash a rom and then it didnt work out so well (phone still lights up, drivers are not compatible).
I all else fails I can attempt the neurtino rom (as long as you dont have to install from sd card zip file because I cannot!)
the neutrino is an Atrix 4G rom only, so you cant use it and it also needs to be installed via internal so its a no go either way. isnt your phone the china "htc" model? i dont have much user time on an htc so im not too sure what you can do?
again id try to find a barebones that you can flash the way you did with the rom that gave you errors. ill try to do some searching too and see what i can find. let me know if you get anything workin! and if there is someone else out there that can enlighten the both of us help would be appreciated!
and isnt yours like an evo 4g? maybe one of those roms will work?
Thanks for your response and suggestions. I will try to dish up a small tutorial with how far I can get in the backup/flashing process. I can check for an evo 4g rom and see what the specs are. The current rom I used i believe works, but doesnt have the video driver so the screen has no image. I believe each partition of ram has a set size so you can only flash a rom for the mt6573 chipset which will fit in the available space for each partition and also happens to contain the video, audio, bluetooth, etc drivers.
I have used SP Flash Tool and was able to backup all of the partitions of my working phone but the SP Flash Tool gives all sorts of errors when I try to load the files and flash them to my non-working phone.
The funny thing is that I downloaded files for a different phones rom and was able to flash those to the non-working phone, as mentioned in my previous post, which allows the phone to power on, but the phone doesnt work besides lighting up.
I know it is possible to make a backup of my good phone and flash that rom onto my non-working phone, I just dont know what I am doing wrong.
So far, this is what I have done . . .
1. Installed SDK tools for android
2. Obtained my scatter txt file by using command prompt
3. Used MTKRomStudio to open that file which tells me the addresses of all the partitions and their file sizes
4. Used SP Flash Tool V.2.11.29.00 to "readback" (backup) each individual rom file (preloader, uboot, bootimg, android, dsp, etc)
5. Confirmed the file sizes of each of the above files to what MTKRomStudio said the file size should be
6. Attempted to load these files into SP Flash Tool and get errors such as "partition too large, failed to load", or "partitions overlap".
7. I was able to open some of the partitions such as android, and usrdata but when attempting to flash I receive errors such as "dram error".
8. I was able to download an entire backup of all "readback" files for a different model phone, and each one of those files loaded fine and downloaded to my non-working phone.
9. Just to mention, my non-working phone was completely dead (no power up, no lights) before I flashed the random phone rom I found online, and now at least it powers up (lights up).
Anyone have any information? I have created a small visual representation of what I have been looking at and messing around with. Let me know!
Mt6573 phone flash help
Hi all, I need help. I used sp flash tool and flashed the original files to my phone. I then restarted the phone and it would not go past the blue android screen. I let se overnight and still no success. After that i flash the boot and still no progress. Finally i flashed the uboot and now it only lights up but no picture at all. I have used sp flash to try to flash the entire file system back to the mt6573 but it will not flash the recovery, android, or sec_ro files. Can anyone help?
CrimsonX said:
Hi all, I need help. I used sp flash tool and flashed the original files to my phone. I then restarted the phone and it would not go past the blue android screen. I let se overnight and still no success. After that i flash the boot and still no progress. Finally i flashed the uboot and now it only lights up but no picture at all. I have used sp flash to try to flash the entire file system back to the mt6573 but it will not flash the recovery, android, or sec_ro files. Can anyone help?
Click to expand...
Click to collapse
Same problem here except I can't flash dsp and preloader
UPDATE : flash worked finaly.my phone is fixed
Sent from my GT-P5110 using xda app-developers app
Whistler011 said:
Same problem here except I can't flash dsp and preloader
UPDATE : flash worked finaly.my phone is fixed
Sent from my GT-P5110 using xda app-developers app
Click to expand...
Click to collapse
Please share how you did it, i'm in the same position with a MT6573 phone that are stuck on boot, and wont accept the preloaderfile
nsxtas said:
Please share how you did it, i'm in the same position with a MT6573 phone that are stuck on boot, and wont accept the preloaderfile
Click to expand...
Click to collapse
Same here.
Can somebody please post all the files .
I have an Alcatel one touch 918 not d/m/n
It`s the second phone that i have bricked.
Sharing it`s caring.
LeStonga said:
4. Used SP Flash Tool V.2.11.29.00 to "readback" (backup) each individual rom file (preloader, uboot, bootimg, android, dsp, etc)
Click to expand...
Click to collapse
I'm using MTK6573 phone but could i know how do you start the "readback" using SP Flash. I'm not able to start it while holding VOL-UP button and connect the USB data cable into your phone. Are there any other methods to start it. Thanks for your help.
CM
Why don't you make a try with CyanogenMod?
LeStonga said:
Thanks for your response and suggestions. I will try to dish up a small tutorial with how far I can get in the backup/flashing process. I can check for an evo 4g rom and see what the specs are. The current rom I used i believe works, but doesnt have the video driver so the screen has no image. I believe each partition of ram has a set size so you can only flash a rom for the mt6573 chipset which will fit in the available space for each partition and also happens to contain the video, audio, bluetooth, etc drivers.
I have used SP Flash Tool and was able to backup all of the partitions of my working phone but the SP Flash Tool gives all sorts of errors when I try to load the files and flash them to my non-working phone.
The funny thing is that I downloaded files for a different phones rom and was able to flash those to the non-working phone, as mentioned in my previous post, which allows the phone to power on, but the phone doesnt work besides lighting up.
I know it is possible to make a backup of my good phone and flash that rom onto my non-working phone, I just dont know what I am doing wrong.
So far, this is what I have done . . .
1. Installed SDK tools for android
2. Obtained my scatter txt file by using command prompt
3. Used MTKRomStudio to open that file which tells me the addresses of all the partitions and their file sizes
4. Used SP Flash Tool V.2.11.29.00 to "readback" (backup) each individual rom file (preloader, uboot, bootimg, android, dsp, etc)
5. Confirmed the file sizes of each of the above files to what MTKRomStudio said the file size should be
6. Attempted to load these files into SP Flash Tool and get errors such as "partition too large, failed to load", or "partitions overlap".
7. I was able to open some of the partitions such as android, and usrdata but when attempting to flash I receive errors such as "dram error".
8. I was able to download an entire backup of all "readback" files for a different model phone, and each one of those files loaded fine and downloaded to my non-working phone.
9. Just to mention, my non-working phone was completely dead (no power up, no lights) before I flashed the random phone rom I found online, and now at least it powers up (lights up).
Click to expand...
Click to collapse
I have a MT6575 phone and I have exactly your nr. 7 issue (BROM ERROR:S_DL_GET_DRAM_SETTING_FAIL(5054)). Were you able to get this working somehow? I am confident that the selected partitions are for this phone as I read them out myself. But flashing back won't work. Does anyone have any leads?
e-lime said:
I have a MT6575 phone and I have exactly your nr. 7 issue (BROM ERROR:S_DL_GET_DRAM_SETTING_FAIL(5054)). Were you able to get this working somehow? I am confident that the selected partitions are for this phone as I read them out myself. But flashing back won't work. Does anyone have any leads?
Click to expand...
Click to collapse
If you have the correct files use the newest version:
http://forum.xda-developers.com/showthread.php?t=1982587
It is easy to mess things up if you try random files.
MTK 6577 and SP Flash Tool
I too am also having problems with the flash tool. I am trying to help a friend bring his chinese note 2 clone back to life. He somehow got CWM onto the phone and the custom recovery seems to be functioning properly, but I cant find any sort of ROM file to flash in recovery.
Now I am going back and trying to restore the phone to factory using the flash tool. Installed the VCOM drivers, then went to load the scatter file we obtained from the factory (Bro Tech) it says the scatter file is incorrect format?
My question is: are there any roms we could try to flash on this phone from CWM or do we have to use the Flash Tool? I'm hoping since CWM seems to be working that I can simply flash an acceptable rom with that instead of trying to find a scatter file.
Maybe someone can suggest some ROMs to try flashing with CWM. The phone is: Goophone N2 7100 I believe. Thanks for reading, I really want to help him resurrect this interesting piece of copyright infringement (the phone looks amazingly like a Note 2 till you get close to it)
Evita Carbonized
GTab 2 7 AOKP'd
DollarStrawz said:
I too am also having problems with the flash tool. I am trying to help a friend bring his chinese note 2 clone back to life. He somehow got CWM onto the phone and the custom recovery seems to be functioning properly, but I cant find any sort of ROM file to flash in recovery.
Now I am going back and trying to restore the phone to factory using the flash tool. Installed the VCOM drivers, then went to load the scatter file we obtained from the factory (Bro Tech) it says the scatter file is incorrect format?
My question is: are there any roms we could try to flash on this phone from CWM or do we have to use the Flash Tool? I'm hoping since CWM seems to be working that I can simply flash an acceptable rom with that instead of trying to find a scatter file.
Maybe someone can suggest some ROMs to try flashing with CWM. The phone is: Goophone N2 7100 I believe. Thanks for reading, I really want to help him resurrect this interesting piece of copyright infringement (the phone looks amazingly like a Note 2 till you get close to it)
Evita Carbonized
GTab 2 7 AOKP'd
Click to expand...
Click to collapse
Create personalized file scatter for your device with MTK Droid. Here: http://forum.xda-developers.com/showthread.php?t=2160490
[email protected] said:
Same here.
Can somebody please post all the files .
I have an Alcatel one touch 918 not d/m/n
It`s the second phone that i have bricked.
Sharing it`s caring.
Click to expand...
Click to collapse
Have a alcatel 4033a Phone Got bricked and needs to be flash any help on that ..? plz i need help
Alecupid said:
Have a alcatel 4033a Phone Got bricked and needs to be flash any help on that ..? plz i need help
Click to expand...
Click to collapse
hi, i've made a mistake.
I've installed an odex version from a modified recovery(with dalvick cache). Can anyone help me?

Unbrick Assistance Thread

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

General OnePlus Nord N200 5G DE2118 Finally Unbricked.....

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

Categories

Resources