Is there any way to create a debrick.img from a downloadable stock rom? (Sammobile). I know you can create a debrick.img from a working phone, but I want to know if it's possible to do it from the rom itself (with hopefully Windows).
I *think* I may have figured this out. My phone might need a USB Jig and maybe that's why it's still not working for me, but if someone else with a bricked phone wants to test this, please let me know your results. Here is how you can create a debrick.img from the stock ROM.
1) Download and install 7-Zip: https://sourceforge.net/projects/sevenzip/
2) Download and install OSFMount: http://www.osforensics.com/tools/mount-disk-images.html
3) Download your stock ROM (if you haven't already). For example, here is mine for the SGH-I257M (I257MVLUAMK5): http://www.sammobile.com/firmwares/database/SGH-I257M/FMC/
4) Download a debrick.img (I suppose any kind will do; like one of these: https://drive.google.com/folderview?id=0B612qYHFMILfWUlMTTEwdUstcXM&usp=sharing)
5) Unzip contents of stock ROM download
6) You will see a .tar.md5 file (mine is I257MVLUAMK5_I257MOYAAMK5_I257MVLUAMK5_HOME.tar.md5)
7) Right click on this file and go to 7-Zip > Open Archive (you might get an error like I did; ignore it)
8) In my file, I saw something called NON-HLOS.bin. I dragged it out of Z-Zip onto my desktop to extract it.
9) Right click on NON-HLOS.bin and go to 7-Zip > Open Archive.
10) You will see a folder called "image." I dragged and dropped this onto my desktop as well.
11) Open OSFMount and click on "Mount new..." and choose the "..." button to choose your debrick.img file.
12) In my debrick.img file, I chose Partition 0 which has 60 MB and says (FAT 12).
13) All the default settings seem fine, but the only thing I changed was unchecking "Read-only drive" near the bottom. Then I clicked OK.
14) Now you will see your drive mounted. Double click on it and you will see a new window pop up with the folder "image."
15) Replace this image folder with your image folder that you saved to your desktop in step 10. Then close the window.
16) Click "Dismount all & Exit."
You're done! Now follow these instructions on how to burn the debrick.img file to a microSD card load onto your phone: http://forum.xda-developers.com/showthread.php?t=2660566
Since I use Windows (Windows 8.1 to be exact), I used win32diskimager-v0.9-binary.zip to burn to my microSD card. I double checked to see if the partitions were there by opening it with MiniTool.
Please, if someone could tell me whether or not this works for them, let me know!
Hello,
thank you very much for your effort! I built one and - Yeah the first try did not seem to work. After the try I wanted to be safe that battery is fully charged, so i plugged it. After a while I saw something on the screen! It might have booted automatically.
Now there are a few lines:
BOOT RECOVERY MODE
Check Boot Partitions..
Copy from T-Flash..
BOOT RECOVERY..
Write 139008 Sectors..
FLASH WRITE FAILURE
ddi: mmc read failed
ODIN MODE
Product Name: GT-I9195
Current Binary: Samsung Official
System Status: Custom
KNOX Kernel Lock: 0x0
KNOX Warranty Lock: 0x0
CSB-Config-LSB: 0x30
BOOTLOADER AP SWAEV: 2
WRITE PROTECTION: Enable
Yeah I think I can now flash with ODIN
Thank you for this post, it might also help others to build their own debrick.img
I will now resume with resurrection
*UPDATE*
Unfortunately I did not succeed in flashing the phone. I think the emmc-Chip has died
First time I flashed, I got an error that there was no PIT.
Then I added one and said "re-partition" in ODIN.
It now found the PIT but failed. On the phone there was written a new line in red:
PIT Fail: Total sectors (0)
Well, I do not think I can do anything more. Or do you have any ideas what I could try in addition?
If not then RIP my beloved S4 Mini.
But this has nothing to do with the topic. The method described to create a debrick out of a stock rom is possible and it was successful.
That's funny that you mention it's an S4 mini. I know I posted in the S6 section about this, but only because I was trying to post where there seems to be (possibly) more traffic. And I figured that it's pretty general because it's about creating a debrick.img and not necessarily about debricking a specific phone.
Nobody was answering any of my questions on the other subsections. I also have an S4 mini that I'm trying to debrick. It's the SGH-I257M. I wasn't sure if my debrick.img wasn't working because I tried on a 2GB card and then a 64GB card (both class 10). So I borrowed a 16GB card (class 10), and still nothing is happening. So I'm just leaving it plugged in (like you said). We'll see what happens!
I wondering if there is a problem with the S4 minis dying. It's a friend's phone and he said it kept randomly shutting off. Then one day it just wouldn't turn back on. Maybe it's the battery. Who knows.
upload debrick.img shv e110s please
Samsung SM-G910S HArd Bricked
my samsung SM-G910S no download mode no recovery no bootup.. can anybody plz give me the unbricked debricked img..... From many munths i have been surching about that issue but i dont got success about to clear this issue... dont you people have Samsung SM-G910s in the Word..? becuz i googled about this model but every where in the world that bloody file dont have to any body... hay guyz help if you can... :crying:
how does this worn if you haven`t a stock rom on your dead phone (i9195) but a custom lineage-14.1 ?
anyone said:
how does this worn if you haven`t a stock rom on your dead phone (i9195) but a custom lineage-14.1 ?
Click to expand...
Click to collapse
did anyone edit my post?
I had a custom rom lineage-14.1 on it before it suddenly died.
Now following just appear after using a i9195 debrick.img which I found on the forum
" boot recovery mode
check boot partitions. .
copy from t-flash. ."
But I`m still not able to start the download mode for odin
need a debrick image
will this work if the phone rom is not the stock i mean that i flash a coustm rom then the phone bircked if i use a stock debrick img will it work or i must use a another img base on the rom i flashed
Related
Ok, ill keep this quick and tidy. The tab was working just fine. I only used z4 root on it and it still was fine after that. The other day the battery died in it. I plugged it in to charge and now it only boot loops. I put it into recovery mode and i get this as an error.
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
E:can't mount CACHE:recovery/command
*MANUAL MODE*
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
E:Can't mount CACHE:log/recovery.log
E:can't open CACHE:log/recovery.log
E:Cant mount /dev/block/mmcblk0p1
(no such file or directory
I tried using the heimdall program to flash the ed02 files and it still gives this in recovery. Im at my wits end with this and really dont want to send it to sammy. Verizon will not honor the warranty due to the number being disconnected.
Can anyone help me with this so i dont have to send it in. Thanks
1. download heimdall. get it here: http://forum.xda-developers.com/showthread.php?t=755265
2. download the stock verizon files. get them here: http://www.blackmugmedia.com/Android/GT/Mirror/Recovery/CDMA/Verizon/VZW Stock/
you need all four files.
3. download the drivers for the samsung sch-i800. find those here: http://downloadcenter.samsung.com/c...G_USB_Driver_for_Mobile_Phones_v1.3.350.0.exe
4. unzip heimdall. go into the drivers folder, and run zadig.exe. at the top, select 'list all devices'. go to the dropdown menu, and select Samsung Composite USB (i'm pretty sure that's what it was called.) click start, and let it run.
5. open the heimdall front end.
6. put system in system (if you're flashing to ec02, then put factory in system)
put cache into cache
put param into param
put the zimage into both the kernel and recovery slots.
7. turn your tab off, and plug it into the computer using USB. hold down the power and the volume down buttons until you see the little droid dude with a shovel.
8. click the start button on heimdall.
9. wait for the flash to complete (don't unplug your device, obviously, during the flashing.) once your phone reboots, it's okay to unplug it.
10. now, boot into the stock recovery, and wipe data and cache. reboot, and update to ec02.
11. enable usb debugging.
12. plug your phone back in to the computer.
13. now run superoneclick for root. get that here: http://forum.xda-developers.com/showthread.php?t=803682
14. either play with it in stock, or go find oldmacnut's excellent Better Than Life Rom, and follow the instructions to flash that.
15. enjoy your tab!
boodafli said:
1. download heimdall. get it here: http://forum.xda-developers.com/showthread.php?t=755265
2. download the stock verizon files. get them here: http://www.blackmugmedia.com/Android/GT/Mirror/Recovery/CDMA/Verizon/VZW Stock/
you need all four files.
3. download the drivers for the samsung sch-i800. find those here: http://downloadcenter.samsung.com/c...G_USB_Driver_for_Mobile_Phones_v1.3.350.0.exe
4. unzip heimdall. go into the drivers folder, and run zadig.exe. at the top, select 'list all devices'. go to the dropdown menu, and select Samsung Composite USB (i'm pretty sure that's what it was called.) click start, and let it run.
5. open the heimdall front end.
6. put system in system (if you're flashing to ec02, then put factory in system)
put cache into cache
put param into param
put the zimage into both the kernel and recovery slots.
7. turn your tab off, and plug it into the computer using USB. hold down the power and the volume down buttons until you see the little droid dude with a shovel.
8. click the start button on heimdall.
9. wait for the flash to complete (don't unplug your device, obviously, during the flashing.) once your phone reboots, it's okay to unplug it.
10. now, boot into the stock recovery, and wipe data and cache.
11. enable usb debugging.
12. plug your phone back in to the computer.
13. now run superoneclick for root.
14. either play with it in stock, or go find oldmacnut's excellent Better Than Life Rom, and follow the instructions to flash that.
15. enjoy your tab!
Click to expand...
Click to collapse
nice guide though .... keep it up
can you tell me this guide for which tab i'm sure is not for the galaxy tab GSM
as i have sticky thread and i have empty place i'll like to add this guide sure after your proving
edit i got it , its for CDMA .. so can you accept that i post this guide under your name in my thread ?
it's for the verizon CDMA tab. and you can post it, it's supposed to be helpful. i lurked on these boards for like, 2 months before i got brave enough to try doing stuff to my tab. having a step by step process really made me feel like i was flashing with at least a little bit of a safety net.
k0sh said:
can you tell me this guide for which tab i'm sure is not for the galaxy tab GSM
as i have sticky thread and i have empty place i'll like to add this guide sure after your proving
Click to expand...
Click to collapse
oh hey. in your sticky, add this after 'now run superoneclick': get that here: http://forum.xda-developers.com/showthread.php?t=803682
boodafli said:
oh hey. in your sticky, add this after 'now run superoneclick': get that here: http://forum.xda-developers.com/showthread.php?t=803682
Click to expand...
Click to collapse
will do sure , thanks
go check it here Post number 3
http://forum.xda-developers.com/showthread.php?p=14929111#post14929111
Ok i downloaded all the files and it is still looping on me. I went into the recovery and it is still giving me the same errors. Im at a loss here. I think it just may have to go to sammy. Im not that good with this. I really do appriciate all the help.
when you're in recovery, does it let you wipe cache and data? maybe try that, then reflash?
I tried with the updated version and e2 version of the software and anytime i go into the recovery its giving me that same line of errors. I think it might be a soft/hard brick. I may have to send it in to get serviced. Im just glad that if i do the stock software is flashed to it and they wont be able to tell the difference.
Edit:
Well after doing some digging it seems that the recovery partition cannot be loaded onto the disk. It looks like the internal sd card itself might be corrupt or fried. I have adb that i can try to do it with, but im just tempted to send it in. I am just hoping that they dont say that its no longer warranted.
Hi,
I was trying to upgrade to Gingerbread, and downloaded the FW files from samfirware.com. I used Odin to flash, everything turned out successful, except that my tab gets stuck at the Samsung logo screen. Any help would be appreciated?
Thanks
if you have a verizon tab, we don't have gingerbread yet. if you have a GSM tab, try booting into recovery, wiping cache, data, and dalvik, and rebooting. beyond that, since i don't have a GSM tab, i dunno what to tell you.
ashish.b said:
Hi,
I was trying to upgrade to Gingerbread, and downloaded the FW files from samfirware.com. I used Odin to flash, everything turned out successful, except that my tab gets stuck at the Samsung logo screen. Any help would be appreciated?
Thanks
Click to expand...
Click to collapse
Well samsung has fixed it for me. they had to replace the entire control board. I guess i really did a number on it. Whats cool is that its not going to be a verizon tab anymore. They have the hardware for it but the rom is stock like it was bought off the shelf. I cant believe it would fry like that after just charging.
hi guys....
i have a i9000.......... with soft-brick, i use a jig (301k whit miniusb ), and access to download mode and flashed a stock rom......
but the internal memory, keeps previous programs and gives me FC, with CWM recovery after doing full wipe, and format the internal memory, restarting the computer maintains all, do not delete anything ........
now get a message that the internal sd is damaged, but not allow me to enter mode debbug because the phone is freeze ... I also recognize the pc to format the external memory .........
as I can do to install a ROM CM-10, in the external memory?
thanks for the help.
sorry for my eng.
You say the message says your internal SD is damaged. What EXACTLY does the message say?
Sent from my GT-I9000 using Tapatalk 2
try this! http://forum.xda-developers.com/showthread.php?t=1906089 i don't have an sgs, so i can't tell you if it works and i can't help you, but in that thread you can find someone to help you
I was having the same problem and found the solution here
I was having the same problem and found the solution here http://forum.xda-developers.com/showpost.php?p=35585404&postcount=8
this is my post to thanks for the kernel
http://forum.xda-developers.com/showpost.php?p=38210629&postcount=12
look for a sd fast I have a class 4 and was too slow and buy a class 10 and now works just like new.
far2 said:
I was having the same problem and found the solution here http://forum.xda-developers.com/showpost.php?p=35585404&postcount=8
this is my post to thanks for the kernel
http://forum.xda-developers.com/showpost.php?p=38210629&postcount=12
look for a sd fast I have a class 4 and was too slow and buy a class 10 and now works just like new.
Click to expand...
Click to collapse
Thank you.
I flash the kernel but got a boot loop.
I have the firmware JW4 not get the JVU ... my model is i9000t, could you help me get the firmware that worked with your phone.
Thanks in advance.
sorry for my English.
solved!!!
Downloading the ROM file: I9000XXJVU_I9000OXAJVU_OXA.rar
Downloading the ODIN & PIT files: Flashprogram_Samsung_I9000__Pits.rar
Downloading the Drivers for the PC: SAMSUNG_USB_Driver_for_Mobile_Phones_v1_3_2300_0.zip
Most importantly: KEEP YOUR PHONE FULL CHARGED OR AT-LEAST ABOVE 50% CHARGING LEVEL.
Once you are done with the prerequisites, you can move down to the installation procedure as below:
1. Unzip the ROM, ODIN and Drivers to their respective folders in case it requires any password, it will be “samfirmware.com”
2.Now, the first thing to be done is install the phone drivers on the PC which you are to use for flashing the ROM. To do this, navigate to SAMSUNG_USB_Driver_for_Mobile_Phones_v1_3_2300_0 folder and select the appropriate setup x86 or x64 based on the type of OS you are using on your PC.
Once this one has been installed, get your GT I9000 in the download mode by using the 3-Button combo. For that, first switch off the phone and wait for it to vibrate a little just to confirm that it is completely switched off. Then, press the three buttons: Power Key, Volume Down and Home Key and hold until you see a green android saying “Downloading”
3. Next, goto Flashprogram_Samsung_I9000__Pits folder and open I9003_Odin3 v1.82.exe (Don’t bother the I9003 in the file name. It is compatible for I9000 also)
4.Once ODIN has be opened, connect your phone to the PC while it is in download mode. Once connected, an “Added” remark will appear on the message window.
5. Next, click on the PIT button, navigate to the Flashprogram_Samsung_I9000__Pits folder and select s1_odin_20100512.pit
6. Then, click on the PDA button, navigate to the I9000XXJVU_I9000OXAJVU_OXA folder and select the CODE_I9000XXJVU_CL851880_REV03_user_low_ship.tar.md5 file.
7. Then, click on the PHONE button, navigate to the I9000XXJVU_I9000OXAJVU_OXA folder and select the MODEM_I9000XXJVU_REV_00_CL1092175.tar.md5 file.
8. Then, click on the CSC button, navigate to the I9000XXJVU_I9000OXAJVU_OXA folder and select the GT-I9000-CSC-MULTI-OXAJVU.tar.md5 file.
PLEASE MAKE SURE TO SELECT THE FILE PROPERLY AS ABOVE AND DOUBLE CHECK BEFORE CONTINUING FURTHER.
9. Next, make sure that Re-Partition, Auto Reboot and F. Reset Time have been check marked.
Once all the above steps are done, click on Start button and wait for the message window to show “All threads completed” and “Pass” displayed on the top left box.
10. Then, click on PDA button, navigate to Kernel_JVU_Fix_sdcard file, and clic on Start!
and viola!!!
thanx far2
I glad this Solve the SGS problem for you
gerickt said:
solved!!!
and viola!!!
thanx far2
Click to expand...
Click to collapse
I glad this Solve the SGS problem for you, and all the people in the forum, hope some developer can make a kernel like this but for the new jw4+ or even better for the cm9 or cm10
I know some people has install the cm9 and cm10 do but they have a total sd failure, our sd is still readable and is even worse.
Gerickt yesterday I write to you a PM in Spanish wit more indication to you did you receive?
PD: nice you made a detail description for the procedure :good:
the developer answer to my
rxxxni was the developer to post the kernel here and he just answer the place to look for more info in his kernel here
htcmania.com/showthread.php?t=520348
I don't know if this is bad to post other links outside the xda but he made the kernel and there is more info
Hi there, only just joined site as have had problem with this phone for a while now but left it alone untill my GF nagged me to try and fix it, but am very stuck and confused so here it goes....
the phone's carrier was virgin mobile so i downloaded an app to unlock it to another carrier but phone froze during process so had to power off and on the it got stuck on logo screen so some how i managed to install twrp v2.6.3.0 onto the phone but i am now just stuck here the phone now has no operating system and it showing internal memory as 0mb and i can only mount external SD.
Please if someone can help me i would be very very happy as its driving me crazy...serious.
Hope this post is in the correct section and any other info required i can give if needed.
Thanks in advance
John
johnlfc81 said:
Hi there, only just joined site as have had problem with this phone for a while now but left it alone untill my GF nagged me to try and fix it, but am very stuck and confused so here it goes....
the phone's carrier was virgin mobile so i downloaded an app to unlock it to another carrier but phone froze during process so had to power off and on the it got stuck on logo screen so some how i managed to install twrp v2.6.3.0 onto the phone but i am now just stuck here the phone now has no operating system and it showing internal memory as 0mb and i can only mount external SD.
Please if someone can help me i would be very very happy as its driving me crazy...serious.
Hope this post is in the correct section and any other info required i can give if needed.
Thanks in advance
John
Click to expand...
Click to collapse
if you've got a working CWM or TWRP Recovery then it should be easy to flash a new firmware onto the phone. I haven't done this but try the following steps :
1. Download this http://www.ipho9.com/install-dmod-custom-rom-galaxy-s3-mini-gti8190/ custom ROM
2. DO NOT extract it (keep the .zip file, well, zipped )
3. Copy/Paste the above .zip file to your external sd card
4. Start the phone and go to recovery (power+home+volume up buttons)
5. Choose install zip from external sd card
6. Find the .zip file that you just copied and select it
7. Now wait until it installs (can take about 10 mins or more - just be patient)
8. Reboot phone when the installation of the ROM is complete
9. Have fun with your completely new S3 Mini with a new great S4 look&feel
Hope that works !
koragg97 said:
if you've got a working CWM or TWRP Recovery then it should be easy to flash a new firmware onto the phone. I haven't done this but try the following steps :
1. Download this http://www.ipho9.com/install-dmod-custom-rom-galaxy-s3-mini-gti8190/ custom ROM
2. DO NOT extract it (keep the .zip file, well, zipped )
3. Copy/Paste the above .zip file to your external sd card
4. Start the phone and go to recovery (power+home+volume up buttons)
5. Choose install zip from external sd card
6. Find the .zip file that you just copied and select it
7. Now wait until it installs (can take about 10 mins or more - just be patient)
8. Reboot phone when the installation of the ROM is complete
9. Have fun with your completely new S3 Mini with a new great S4 look&feel
Hope that works !
Click to expand...
Click to collapse
1. Download this http://www.ipho9.com/install-dmod-custom-rom-galaxy-s3-mini-gti8190/ custom ROM
Click to expand...
Click to collapse
you can download every ROM you want for s3 mini (somin.n, Virginity, CM, ...) - steps 2 - 9 are the same
good luck
JackoMJ is right. I just posted the one i'm on 'cause i know that all the stuff are working
@MikeChannon removed OP. please close
what? lol
hi ionioni,
many thanks for your tool. I could successfully create a signed bios file. During the flashing process, i believe, it shows no errors. But after a automatically reboot just the teclast logo appears.
I did a "RESTORE DEFAULT" and "SAVE AND RESET" but when i try to flash android with the mirek tool, it shows the same error message (get_path:344...) .
Do you have any suggestions what i can try to restore a working state?
Thank you.
the_dude_84 said:
During the flashing process, i believe, it shows no errors. But after a automatically reboot just the teclast logo appears
Click to expand...
Click to collapse
at the end of the bios flashing, before the reboot, did you received a "RESTORE COMPLETED! Rebooting the tab to load new BIOS!" message? if not, what messages you got when flashing? what are the steps you are doing? more details ... this tool job is to write a (user provided) bios file, not fixing specific stuff (other) on your tab
later edit: the error 'get_path:344' is normal to be shown. the x98 bootloader (efilinux file) will at first try to get a handle for the device (disk) it was started from, but when it is run directly from the bios, ie dnx mode (normally it loads/executes from his EFI partition on mmc) the call returns no handle (as it should) and this is causing the message. is a normal message if starting from dnx, what is not normal, is if after that the bootloader won't be able to load and execute the kernel from the passed boot image.
the tablet just restarts without such a message you named. I used my prevously saves bios with your tool and flash it. What steps i can do to convince the tablet to start the kernel?
Did you repair the saved BIOS before flash by this new tool?
You have to change from FE FE at 400Dh and 400Eh address to FF FF with a hex editor!
updated OP with v2 of the tool as it seems these x98 tabs are not having the most conforming EFI firmware in the bios (it 'forgets' the consistent mapped device so i hard-coded it in the tool, it would have map to the same path anyways as it is a consistent /virtual/ disk that is used as environment during the flashing, so this 'patch' just helps the non-conforming devices /such as x98 so far/ not limits)
blackbile said:
Did you repair the saved BIOS before flash by this new tool?
You have to change from FE FE at 400Dh and 400Eh address to FF FF with a hex editor!
Click to expand...
Click to collapse
do you know what those two bytes are about? can anyone say that he bricked his tab by flashing a FE FE bios? (i have flashed my bios back dozen times so far on my Lenovo and did not knew about this until read someplace on these posts so i checked my backup bios file and sure thing it did have the FE FE inside at that offset... i guess is something wrong with my tab since it did not bricked )
joke aside, i cannot say whether this IS or IS NOT true, but what i can say is that there were two users i assisted in flashing back their bios backup (on x98 models) and both had FE FE at that offset and they did NOT BRICKED ( @florent.m was on ant the other don't recall)... i wish i knew more about WHY this needs to be done, not just YOU MUST instructions... what i know is that area belongs to the nvram of TXE region (is the EFFSOSID partition of it) but since Intel takes care that no one has access to TXE related info i sure would be interested in someone saying what those two bytes are accounted for (and more of course)...
again someone who has a flash programmer can check easily and safely (i have but as i said i cannot hard-brick it )
I'm still not able to flash. I get this error message upon running fastboot boot image_name.img
Code:
INVALID size (7586586 bytes) for pushed package! This tool will only accept a (md5) BIOS file for input. You MUST run md5add.exe on your BIOS file and push the file it produces.
ABORTING
I did run md5add on the img and I did run fastboot boot on the image it produced (16 bytes larger than the original). What am I doing wrong?
BTW, by pushing does it mean that I have to run anything else besides those 2 commands on fastboot?
andrepd said:
I'm still not able to flash. I get this error message upon running fastboot boot image_name.img
Code:
INVALID size (7586586 bytes) for pushed package! This tool will only accept a (md5) BIOS file for input. You MUST run md5add.exe on your BIOS file and push the file it produces.
ABORTING
I did run md5add on the img and I did run fastboot boot on the image it produced (16 bytes larger than the original). What am I doing wrong?
BTW, by pushing does it mean that I have to run anything else besides those 2 commands on fastboot?
Click to expand...
Click to collapse
read the op again !!! and do exactly the steps detailed there!!! you need to use YOUR signed bios file generated with md5add ... instead you are WRONGLY!!! using some boot image file (luckily for you there is a size check too, otherwise you would have been flashing a kernel on your bios chip, oh boy...)
again:
the first instruction pushes the bios efi flasher tool
the second one pushes YOUR bios (signed) file that you want to flash on your bios chip. to make sure that the bios file that is wrote by the tool is not altered during the transfer i added the extra md5 signing step, so before it will start the effective flashing the efi tool will check the bios file received against the md5 signature appended (this step is normally not needed, but on some PC could be that the usb transfer misbehaves)
Thanks a lot for your efforts and help!!!
ionioni said:
read the op again !!! and do exactly the steps detailed there!!! you need to use YOUR signed bios file generated with md5add ... instead you are WRONGLY!!! using some boot image file (luckily for you there is a size check too, otherwise you would have been flashing a kernel on your bios chip, oh boy...)
again:
the first instruction pushes the bios efi flasher tool
the second one pushes YOUR bios (signed) file that you want to flash on your bios chip. to make sure that the bios file that is wrote by the tool is not altered during the transfer i added the extra md5 signing step, so before it will start the effective flashing the efi tool will check the bios file received against the md5 signature appended (this step is normally not needed, but on some PC could be that the usb transfer misbehaves)
Click to expand...
Click to collapse
But the image I'm flashing isn't even 7586586 bytes... I'm flashing with this tool as per this post http://forum.xda-developers.com/showpost.php?p=64854157&postcount=26 (img in the OP of that thread)
Sorry I'm a bit confused... Is that boot image the wrong one to flash then?
Thank you very much!
I think it worked and is waiting for input or is even done already, but I'm quite cautious now, so I don't want to press anything yet
It says:
FPT operation passed
_
Click to expand...
Click to collapse
In the flash.bat from another tool (TTT-Update the BIOS on your X98 Air II/3G to the latest dual boot version) it should write that status to a log file and continue with either flash passed or failed, but apparently it doesn't continue automatically in my case.
Hope anyone knows if it is safe to do anything. I've pressed the power button shortly as a confirmation command, but that doesn't do anything.
andrepd said:
But the image I'm flashing isn't even 7586586 bytes... I'm flashing with this tool as per this post http://forum.xda-developers.com/showpost.php?p=64854157&postcount=26 (img in the OP of that thread)
Sorry I'm a bit confused... Is that boot image the wrong one to flash then?
Click to expand...
Click to collapse
This is a DIFFERENT tool! that one you are refering to already has a BIOS file in it...
This one flashes a bios file YOU MUST provide!
Bolsnerk said:
Thank you very much!
I think it worked and is waiting for input or is even done already, but I'm quite cautious now, so I don't want to press anything yet
It says:
In the flash.bat from another tool (TTT-Update the BIOS on your X98 Air II/3G to the latest dual boot version) it should write that status to a log file and continue with either flash passed or failed, but apparently it doesn't continue automatically in my case.
Hope anyone knows if it is safe to do anything. I've pressed the power button shortly as a confirmation command, but that doesn't do anything.
Click to expand...
Click to collapse
As said on some x98 devices (having a specific bios?) it seems that after the bios is flashed 100% it hangs... not so much you can do but force a power off/reboot ... you should be fine
ionioni said:
This is a DIFFERENT tool! that one you are refering to already has a BIOS file in it...
This one flashes a bios file YOU MUST provide!
Click to expand...
Click to collapse
Okay, I got it working, phew, I was being a total noob and confusing everything. I took the dual boot BIOS, added the md5 hash with the tool you provided and flashed it with your tool. Everything went well. Thank you for your work and sorry for being a total moron
andrepd said:
Okay, I got it working, phew, I was being a total noob and confusing everything. I took the dual boot BIOS, added the md5 hash with the tool you provided and flashed it with your tool. Everything went well. Thank you for your work and sorry for being a total moron
Click to expand...
Click to collapse
Excellent!
ionioni said:
do you know what those two bytes are about? can anyone say that he bricked his tab by flashing a FE FE bios? (i have flashed my bios back dozen times so far on my Lenovo and did not knew about this until read someplace on these posts so i checked my backup bios file and sure thing it did have the FE FE inside at that offset... i guess is something wrong with my tab since it did not bricked )
joke aside, i cannot say whether this IS or IS NOT true, but what i can say is that there were two users i assisted in flashing back their bios backup (on x98 models) and both had FE FE at that offset and they did NOT BRICKED ( @florent.m was on ant the other don't recall)... i wish i knew more about WHY this needs to be done, not just YOU MUST instructions... what i know is that area belongs to the nvram of TXE region (is the EFFSOSID partition of it) but since Intel takes care that no one has access to TXE related info i sure would be interested in someone saying what those two bytes are accounted for (and more of course)...
again someone who has a flash programmer can check easily and safely (i have but as i said i cannot hard-brick it )
Click to expand...
Click to collapse
IonIoni,
All,
1st - thanks again for your tool, it saved my tablet (teclast C5J8)
2nd - yes the boot file I provided to Ionioni was untouched, a direct copy of the bios as dumped by mirek backup tool, and up to now, everything is working fine, either on android, or on Windows 10.
and when I say everything fine......I want to say as before..........the GPS is still not working (((((((
thanks a lot,
Cheers,
Florent
Holy moley, the last 24 hours have been intense, that is how old my x98 air iii is, and I have read over a thousand pages here on XDA in that time, i've also managed to soft brick it trying to flash a dual boot bios as per Techknights/Techtablets guides, not sure why or where exactly things went bad, now i'm stuck in a boot loop, red Chinese symbols with a tiny arrow beside it, but reading this gives me some hope, no idea how to follow the simple instructions above when you say..
" IMPORTANT: run the md5add tool on your bios file md5add.exe your_bios_file your_signed_bios_file. "
tried a few things and got nowhere, I tried to open the bios file that you said to place in the same folder as the other two files, with the md5add tool and a small window flashed on screen for a millisecond then disappeared, that's all no file was produced lol
Also not sure what this part means too..
"start in dnx mode and input:
fastboot flash osloader bios_flasher.efi.."
I can get into dnx mode ok but thats all how do I input anything?
My head is fried but I will stay up and try again, it's 5am (Ireland)
Am I missing an elephant in the room? like some other software the everyone else has already installed except noobs like me?
pilot error said:
Holy moley, the last 24 hours have been intense, that is how old my x98 air iii is, and I have read over a thousand pages here on XDA in that time, i've also managed to soft brick it trying to flash a dual boot bios as per Techknights/Techtablets guides, not sure why or where exactly things went bad, now i'm stuck in a boot loop, red Chinese symbols with a tiny arrow beside it, but reading this gives me some hope, no idea how to follow the simple instructions above when you say..
" IMPORTANT: run the md5add tool on your bios file md5add.exe your_bios_file your_signed_bios_file. "
tried a few things and got nowhere, I tried to open the bios file that you said to place in the same folder as the other two files, with the md5add tool and a small window flashed on screen for a millisecond then disappeared, that's all no file was produced lol
Also not sure what this part means too..
"start in dnx mode and input:
fastboot flash osloader bios_flasher.efi.."
I can get into dnx mode ok but thats all how do I input anything?
My head is fried but I will stay up and try again, it's 5am (Ireland)
Am I missing an elephant in the room? like some other software the everyone else has already installed except noobs like me?
Click to expand...
Click to collapse
i wonder how could the instructions in this op be more simple...
you must:
1. find a BIOS file for you model, make sure it is the CORRECT one or you might hard-brick when you flash it
2. sign the file using the md5add tool, this will create a new file, the signed bios file
3. start in dnx mode and load the efi bios flasher tool and then you bios signed file (the steps are in the op)
ionioni said:
i wonder how could the instructions in this op be more simple...
you must:
1. find a BIOS file for you model, make sure it is the CORRECT one or you might hard-brick when you flash it
2. sign the file using the md5add tool, this will create a new file, the signed bios file
3. start in dnx mode and load the efi bios flasher tool and then you bios signed file (the steps are in the op)
Click to expand...
Click to collapse
You know what ionioni, they may be simple to you, but this is my FIRST android tab, its only two days old and it's soft bricked on the very first try at bios flashing from following equally simple instructions from techtablets, flashing new bios from within android using update ifwi.apk, I did exactly that chose the 2.02 dual boot bios that everyone else used, copied it to internal storage and pressed the button.
That is all I did to ruin this tablet lol
What techtablets did NOT mention is he was already rooted on mirek190 v6, that is why my tab is softbricked, not because I chose the wrong files.
No idea how to do this step.. "sign the file using the md5add tool", when i search about it, the only results are back in here?
Can you point me in the right direction to learn about md5add?
Thnk you..
pilot error said:
You know what ionioni, they may be simple to you, but this is my FIRST android tab, its only two days old and it's soft bricked on the very first try at bios flashing from following equally simple instructions from techtablets, flashing new bios from within android using update ifwi.apk, I did exactly that chose the 2.02 dual boot bios that everyone else used, copied it to internal storage and pressed the button.
That is all I did to ruin this tablet lol
What techtablets did NOT mention is he was already rooted on mirek190 v6, that is why my tab is softbricked, not because I chose the wrong files.
No idea how to do this step.. "sign the file using the md5add tool", when i search about it, the only results are back in here?
Can you point me in the right direction to learn about md5add?
Thnk you..
Click to expand...
Click to collapse
i give you the tools and the how-to use them...
again, you need to do this:
1. FIND a bios file for your tab model, ask around and some other owner can point you at it, but take care as this is the file that will be programmed in your tablet so if it is not good you will HARD-BRICK (ask ten times before using it once)
2. after you have found the file, use the md5add tool to sign, if for eg the file is named some_bios_file.bin you can input at a command prompt:
md5add.exe some_bios_file.bin signed_bios.bin (the signed_bios.bin file will be generated)
3. start your tab in dnx mode and input:
fastboot flash osloader bios_flasher.efi
fastboot boot signed_bios.bin and this will start the flashing process... messages will be shown on your tab screen while progressing...
the md5add.exe and bios_flasher.efi files can be found in the attachment to the first post (op)
the bios file is your responsibility to find
when done if the bios file you used is correct you should be able to use again the tab (ie no more bootloop)
i must repeat: be careful what bios file you use, if it's a wrong one you can HARD-BRICK! ask around for that...
Flash the zip file in the link below in twrp recovery and reboot device.go to my files and there you have it your debrick.img 128mb file.save it to microsd card or pc to save your a** someday.so you dont have to look around anymore for debrick image like a little b***h.
extra tip how to unbrick your note 4 any qualcomm based model.ok I'll try to make simple as i can.
THINGS YOU WILL NEED
1,hard bricked note 4
2,microsd card 16 or 32 gb fully formated
3,windows pc
4,micro usb cable
5,windowd32 disk imager software
6,qualcomm usb drivers
7,brain to concentrate
8,Ok now 1st thing install qualcomm usb drivers to pc and restart pc.
9,install windows32 disk imager software to pc
10,connect your microsd card with flash drive in pc
11,open windows32 disk imager software and upload debrick.img that you made and select write to microsd card.
12,after write to microsd card is finish put your microsd card to bricked note 4.
12,press power button for about 10 seconds and it will came back to life if somehow it didn't turn on take battery off and try again
Download link for windows32 disk imager software.
https://mega.nz/#!KdF0nT5K!UGaWv6geTKtNZXRV1fYsch7YfszoEt7N_lXlJwVp--I
Download qualcomm usb drivers link below
https://mega.nz/#!mZFlSb6L!x5qNX3PetAG9myDRi3RuBAi60h-gx59A_alL0K-wWPM
HIT THUMBS UP IF THIS TUTORIAL SAVE YOUR DEVICE SOMEDAY:good:
PLEASE UPLOAD & SHARE YOUR DEBRICK.IMG IN THIS THREAD SO IT WILL BE VERY HELPFUL FOR MANY USERS.
Download zip file to create debrick.image link below.
https://mega.nz/#!bBU1RDwB!tsRI-0DMFyMcw8SVP1b7_nTyLK6xjiLzS6l1eZcJzxM
Thank you
sorry. how can i create debrick.img file ?
ignore. i managed to find debrick.img from another thread. mine is n910G.
theres a different now at least. when i press power on. it vibrates. however still nothing on the screen.
rkaede said:
sorry. how can i create debrick.img file ?
ignore. i managed to find debrick.img from another thread. mine is n910G.
theres a different now at least. when i press power on. it vibrates. however still nothing on the screen.
Click to expand...
Click to collapse
If it vibrate then debrick.img is working
Just leave the device for 5 minutes after it vvibrates
Iy will take you to tfalsh download mode
There you can flash stock firmware in odin using tflash mode in odin options
Just be patient
Press power button and leave phone for 5 to 10 minutes after it vibrates.
thanks. however after i wait for close to 30min. seems nothing. screen still showing blank. doest that mean the debrick.img its not working ?
rkaede said:
thanks. however after i wait for close to 30min. seems nothing. screen still showing blank. doest that mean the debrick.img its not working ?
Click to expand...
Click to collapse
Yes try another debrick image
And make sure debrick should be made from same bootloader as your last bl before bricked cuz if debrick image made from 6.0.1 bl and you ware on 5.1.1 bl then it won't work.you must use same os debrick.img as your last bl.
Hope I won't need it but thanks a lot!
Trex888 said:
Yes try another debrick image
And make sure debrick should be made from same bootloader as your last bl before bricked cuz if debrick image made from 6.0.1 bl and you ware on 5.1.1 bl then it won't work.you must use same os debrick.img as your last bl.
Click to expand...
Click to collapse
thank you. i will check on that thread what is the BL of that debrick.img
i remember it was on 6.0.1
create debrick image
can someone help me how can i create debrick image using partial sys file on step by step tutorial? i have 2 phones hardbricked like galaxy grand neo plus GTI9060i
and galaxy mega GTI9152
because i dont know how to create for my own or would someone provide me the link for image files for my 2 hardbrick phones? i hope this is a miracle to save my phone i just stucked up weeks ago
can it work on all samsung devices
N910p debrick
anybody here have SM-N910P debrick image?
I will search but I would love a link for debrick.img. for N910G. I see some earlier found one..
SAMSUNG NOTE 4 (n910F)Sympthom:
No Vibration, no image, Dead.Hello, i read a lot of foruns and many solutions, but the one i have chosen to persist was the called microSDcard solution and
because it was the way at first the phone reacted by vibrating. But there was no image or any activity on the screen.
Solution/Worked for me:You need to create a microSD card (i used 16Gb SDHC Kingston) with a bootable image placed on a file called "SD4GB.WinDI.img" you can download.
()
- Download "Win32diskImager" and when it finish installing execute it as Admin
- Select the image file "SD4GB.WinDI", choose the MicroSD letter on 'device' and select 'write' option to start writing the microSD card with the image.
- After you need to place the microSD card on the faulty n910F but no need to connect it for now to the computer.
- With the microSD card and the battery placed you can try to make the "Download Mode" sequence and see if it enters on "Download Mode".
If it doesn´t, like it happened to me, my solution was to take out the memory card and the battery for a few seconds, placed the battery and the microSD card
into the n910F again and pressed the power button and the "Down Volume", wich will make it vibrate with no image. Let the phone rest for a few hours without
removing the battery, the microSD card, do not touch in any buttons. After waiting a few hours the first thing you do its to make the "Download Mode" sequence.
- After enter in "Download Mode" connect it to Odin and flash it with option 'nand erase all' cheked also.
- I had to flash it more than once in Odin because the system update didn't went well, and for that booting in "Recovery Mode" and restoring factory and cache solved the problem. Easy it was not enter "Recovery Mode".
I believe it is the emmc memory chip wich heats to much and looses the content of partitions.
When i say a few hours for me i waited to the next morning and it entered "Download Mode". I flashed it, made the factory reset and it booted well in the many times i tried.No need to place download links, Google the file names i gave and the firmware for the n910F
Hope it works for you all also