[HARD BRICK Fixed] - N9005-Make your debrick.img and have it on extSdCard by security

[ValenteL]

See this Thread HERE by @berrg:

[HELP] Galaxy Note 3 n9005 with KitKat (4.4) HARD BRICKED - FIXED!

We all must have the debrick.img on our extSdCard by security. If we have a Hard Brick we can make like this example solved whit success.

I Quote Post #7:

This for another device whit success: http://forum.xda-developers.com/showthread.php?t=2600869. Is same here. Thanks @shazzl

And this the most important: http://forum.xda-developers.com/showthread.php?t=2439367. Thanks @KAsp3rd. All credits to this work HERE.

See also this to create the debrick.img: http://forum.xda-developers.com/showpost.php?p=45725480&postcount=45. Thanks @DocHoliday77

T999 is a example. This Mod work whit Pit.file partition mmcblk0. This is same on all Samsung devices afaik. I only change to N9005_Partial_sys...

If You flashed a new Pit file or Updated by OTA (that can bring one), make new debrick.img .

PS: All People, make your debrick.img and have it on extSdCard by security.

My debrick.img N9005 4.4.2 Kitkat: HERE. Look the THANKS buton if download it.

Flash this Mod attached by Recovery. Saved on internal Sdcard. Copy it to extSdCard.

NOTE: It seems that entire "debricking using microSD" works a little different on Qualcomm-based Samsung phones vs Exynos-based phones - so far all in this thread is about Qualcomm-based models. See post #26 to more details.
Thanks @xclub_101 .

 

[berrg]

See this Thread HERE by @berrg:

[HELP] Galaxy Note 3 n9005 with KitKat (4.4) HARD BRICKED - FIXED!

We all must have the debrick.img on our sdcard by security. If we have a Hard Brick we can make like this example solved whit success.

I Quote Post #7:

This for another device whit success: http://forum.xda-developers.com/showthread.php?t=2600869. Is same here. Thanks @shazzl

And this the most important: http://forum.xda-developers.com/showthread.php?t=2439367. Thanks @KAsp3rd

See also this to create the debrick.img: http://forum.xda-developers.com/showpost.php?p=45725480&postcount=45. Thanks @DocHoliday77

T999 is a example. This Mod work whit Pit.file partition mmcblk0. This is same on all Samsung devices I think. I only change to N9005_Partial_sys...

PS: All People, make your debrick.img and have it on sdcard by security. Flash this by Recovery.

Please note that this is for hard bricked Galaxy Note 3 n9005 with KitKat (4.4)! If you get an unbrick image from 4.3 it wouldn't work!

 

[ValenteL]

Please note that this is for hard bricked Galaxy Note 3 n9005 with KitKat (4.4)! If you get an unbrick image from 4.3 it wouldn't work!

Thanks

I looked inside the updater_script from .zip file and it work only whit Pit file partition mmcblk0. Then if we not flashed a pit file from 4.3 to 4.4 the debrik.img must be the same because the pit file is the same. In this case I think it work.

Anyway, by security is easy make one to 4.3 and another to 4.4.

 

[berrg]

Thanks

I looked inside the updater_script from .zip file and it work only whit Pit file partition mmcblk0. Then if we not flashed a pit file from 4.3 to 4.4 the debrik.img must be the same because the pit file is the same. In this case I think it work.

Anyway, by security is easy make one to 4.3 and another to 4.4.

Could you send me your skype on pm. I would like to ask you sth.

Thanks.

 

[ValenteL]

Could you send me your skype on pm. I would like to ask you sth.
Thanks.

Sorry, I havn't skype and not the pm active. And I don't speak English!!!

 

[FeralFire]

@ValenteL

Everybody knows about this but I don't think many people thought to keep a backup. Everybody would worry of this if and when they got hard bricked. Well, when I say 'everybody', I mean me. So thanks.

 

[ValenteL]

@ValenteL

Everybody knows about this but I don't think many people thought to keep a backup. Everybody would worry of this if and when they got hard bricked. Well, when I say 'everybody', I mean me. So thanks.

I agree. We must remember the people whit this reminder. I'm happy to have helped two members saved Your devices, sending to them the debrick.img.
One Mega 6.3" I9205 and now the Note 3 N9005. And I have already my debrick.img on all my devices.

 

[polish_pat]

thanks

 

[polish_pat]

I agree. We must remember the people whit this reminder. I'm happy to have helped two members saved Your devices, sending to them the debrick.img.
One Mega 6.3" I9205 and now the Note 3 N9005. And I have already my debrick.img on all my devices.

Do you know if this will work if we have a rom installed and are not on stock firmware?

Sent from Note 3 on Rogers

 

[ValenteL]

Do you know if this will work if we have a rom installed and are not on stock firmware?

Look, the debrick.img is made from partition mmcblk0 (PIT) like we can see on updater_script from META-inf of .zip that create it.
One Costumer Rom not touch on Pit file and the Stock Rom, if not have a Pit to flash, is the same. The PIT continue there untouchable.

Then, in my opinion we can make a debrick.img also in this case.

 

[paul_59]

Don't wish to criticise as this has helped some owners, however if you can recover phone function then by definition it wasn't hard bricked.

Widely accepted definition soft bricked is fixable by flashing from pc,

Hard brick is a paper weight unless you've access to jtag kit

Sent from my SM-N9005 using xda app-developers app

 

[hgberry]

Can i use it to create debrick.img on my N900 using @docholliday77 debrick.zip ?
Just flash it in recovery ? Thank You.

 

[FeralFire]

Don't wish to criticise as this has helped some owners, however if you can recover phone function then by definition it wasn't hard bricked.

Widely accepted definition soft bricked is fixable by flashing from pc,

Hard brick is a paper weight unless you've access to jtag kit

Sent from my SM-N9005 using xda app-developers app

Soft brick, by definition, is when the phone won't boot up because it doesn't have a valid OS loaded.
Hard brick is when the phone won't even start and show absolutely no response to things like the power button, charging cable, etc.

 

[ValenteL]

Can i use it to create debrick.img on my N900 using @docholliday77 debrick.zip ?
Just flash it in recovery ? Thank You.

I think Yes. See the update_script from META-inf from .zip Mod. You see that it work only whit partition mmcblk0, the Pit file:

package_extract_file("dd", "/tmp/dd");
set_perm(0, 0, 0777, "/tmp/dd");
ui_print("Data Dump running...");
run_program("/tmp/dd", "if=/dev/block/mmcblk0", "of=/sdcard/debrick.img", "bs=1M", "count=128");;
delete("/tmp/dd");
ui_print("Partial System Dump to debrick.img Complete!!!");

For all that have this partition.

 

[CekMTL]

What if...

I was just wondering... totally off topic but... in these hard brick cases, I understand that the BL (boot loader)/PIT/etc gets somehow corrupted/erased/destroyed... right?

If so, and we do the recovery method by booting with the SD-CARD that has an "old" bootloader (for example someone creates the unbrick image with the oldest bootloader for us), then when trying to flash with odin, it seems (theory here) we should be able to flash older firmwares that have the same BL as the SD-CARDs BL or newer... right?

Then if that is correct, we could come back from 4.4 BL to 4.3 BL ...?

I am asking here because it seems too easy... surely somehow the BL partition should be privilege protected ...?

Hope no one gets mad with my off topic here...just extremely curious
Thank You!

 

[FeralFire]

I was just wondering... totally off topic but... in these hard brick cases, I understand that the BL (boot loader)/PIT/etc gets somehow corrupted/erased/destroyed... right?

If so, and we do the recovery method by booting with the SD-CARD that has an "old" bootloader (for example someone creates the unbrick image with the oldest bootloader for us), then when trying to flash with odin, it seems (theory here) we should be able to flash older firmwares that have the same BL as the SD-CARDs BL or newer... right?

Then if that is correct, we could come back from 4.4 BL to 4.3 BL ...?

I am asking here because it seems too easy... surely somehow the BL partition should be privilege protected ...?

Hope no one gets mad with my off topic here...just extremely curious
Thank You!

Interesting theory.
Now to convince somebody to test it.

 

[CekMTL]

Interesting theory.
Now to convince somebody to test it.

Hahahahahahaha xDDDDDDDDDDDDDDDDD (EXACTLY!)

 

[ValenteL]

I was just wondering... totally off topic but... in these hard brick cases, I understand that the BL (boot loader)/PIT/etc gets somehow corrupted/erased/destroyed... right?

Hope no one gets mad with my off topic here...just extremely curious
Thank You!

Look, this only work if the device is BRICKED whit QHSUSB_DLOAD on screen, I think. We can better ask @shazzl on this Thread how he made for debrick Your Mega 6.3", and read the Threads from @KAsp3rd and @DocHoliday77 on Post #1.
If someone make the same on one Device working it start always by Your boot from Rom installed, not by extSdCard where are the unbrickable partitions (I made a Sdcard and it have 17 partitions, 16 hidden for windows that only see the first from 64 MB). Only if it is nothing to work on Rom all corrupted, it begin by ext Sdcard.

In my opinion, the debrick.img is made from mmcblk0, the Pit file, and have only all partitions to be recreated on device and may be one bootloader. And give us the way to go to Download Mode and flash by Odin one Rom, because inside there are nothing like contents to work.???

Then... just extremely curious This is good, I'm also.

 

[ValenteL]

Interesting theory.
Now to convince somebody to test it.

To test it? How someone can brick his phone to have the QHSUSB_DLOAD, the way to flash by unbrickable sdcard?

Interesting theory.

EDIT: I quote @FeralFire:

I was making a joke.

 

[KAsp3rd]

I was just wondering... totally off topic but... in these hard brick cases, I understand that the BL (boot loader)/PIT/etc gets somehow corrupted/erased/destroyed... right?

If so, and we do the recovery method by booting with the SD-CARD that has an "old" bootloader (for example someone creates the unbrick image with the oldest bootloader for us), then when trying to flash with odin, it seems (theory here) we should be able to flash older firmwares that have the same BL as the SD-CARDs BL or newer... right?

Then if that is correct, we could come back from 4.4 BL to 4.3 BL ...?

I am asking here because it seems too easy... surely somehow the BL partition should be privilege protected ...?

Hope no one gets mad with my off topic here...just extremely curious
Thank You!

Unfortunately this doesn't work. I'm not sure why it doesn't (most likely efuse or signatures not matching in aboot vs firmware) it was tried in the sgsIII thread linked in the OP.

Sent from my Nexus 5 using Tapatalk