[Project Zero] PAC Firmware, PIT file Galaxy S6 collection - Close all softbrick,...

Samsung Galaxy S6/S6 Edge
PAC Firmware/PIT File Collection

"PAC Firmware" is firmware 4 file or 5 file and include the standard PIT file, When you flash "Firmware PAC" partitions to be repair (Not including hard error: "bad sectors", ...), your devices will be cleaned completely!!!
"PAC Firmware" is also full of similar components normal stock firmware.

When do need "PAC Firmware" ?

• Soft brick


• Failed to mount a partition: efs, data, system,... (Not including hard error, example: "bad sectors", ...)


• Failed flash firmware via Odin (stop at a partition: HIDDEN, CACHE,...)


• bootloop


• ...

Download Area
To get "PAC Firmware" not free, Please click the "Thank" button & consider a donation those who share files for you ! :good:

Uploading...

Attached Thumbnails

 

Tab 4 10.1 Odin Rooted, updated SuperSU, softbrick HELP

successfully rooted my Galaxy Tab 4 w/ Odin - when I was prompted to update SuperSU binary, i made the wrong choice to use TWRP/***? instead of Normal -

(had tried "Normal" previously and root failed, likely for some other reason...)

"Unfortunately, Music, SystemUI, etc, etc, etc has stopped" ad continuum... and I can't boot.

I'm sure there's a way out, I'm just not an android geek (web geek).

Can I get some help? VERY MUCH appreciated.

GN
ATL

[REQUEST] Ideas for solving locked bootloader soft-brick

Hey guys, Kyuubi10 here again.
Recently I had an issue with my nexus 9, which is becoming increasingly common.
Where one can permanently soft-brick their nexus, for lack of ticking the "Enable OEM unlock" button, then bootlooping their device while locking their bootloader, thus making it impossible to reflash a system image through fastboot.
If you're lucky enough to still be able to access your custom recovery your device is still salvageable, but if as me you were performing a factory reimage when you locked your bootloader chances are that you have gone back to stock recovery, and only after realised that your OS was bootlooping.

From reading about it, I found out that it was virtually unrecoverable, unless you managed to keep your custom recovery, by either flashing a new system or if your recovery refuses to flash new system you can use this: http://forum.xda-developers.com/nexu...nlock-t3113539.

But in all of these cases you still need a custom recovery.

At the end most people gave up and either bought another device or used their warranty to replace their device (Which I am trying to attempt, if my warranty isn't completely voided.)

So, finally reaching the important point of this thread, I have had a couple ideas which could work to solve this issue but since I don't have enough knowledge I am unable to actually test the idea.
For the device to recognize the lock status of the device even without an OS present means that there must be a flag the bootloader reads. By reading further I found this. http://newandroidbook.com/Articles/Nexus9.html

This basecally explains that Nexus 9 has a partition called PST (Persist) whose only job is to provide the value of this flag. I was wondering whether it is possible by using Linux could get a more direct access to the partition and change its binary value to enable the "enable OEM unlock" variable (Described by fastboot as "Ability is 0").
I had this idea because one day when I bootlooped another device and ADB on windows failed to recognize the device I booted linux and used ADB from there. And the phone was reconized.
This works because Linux can view partitions with different filesystems, where as windowns can only see partitions which have been formatted into "Windows" partitions (e.g. FAT32, NTFS).
So in theory using a Linux OS to access the different partitions in Android should show up much more information, and give you better access. But apart from this I don't know much more. I will be testing this theory out in more detail. But I am challenging the more experienced contributors out there to help out in overcoming this issue!

Please, this is a real issue which is limiting newer nexus devices. If anyone has any new ideas please share by commenting, and lets help each other out to find a solution to this problem.

Soft-brick solution issue

I have left my phone off for 2 days and when i go ahead to start it up it is stuck on the "Samsung galaxy s4"
Logo. I cannot enter recovery, only download mode. I flashed .tar stock file and still that doesn't work. Can anyone help me,?

MT7 TL-10 bringing back to alive after Lollipop softbrick

There are several threads and questions regarding soft brick of MT7 TL-10 after deleting of system in TWRP. Some people referring that installation stucks at 90 percent..i had the same problem..playing in TWRP and suddenly deleting/wiping system and all data..i was trying all possibilities mentioned in this forum..after many hours i succeeded to bring my phone back to business. Now i would like to share my knowledge gained during this process. I own an international version of MT7 TL-10..Before updating to Lollipop and wiping all data i was running B125SP02 firmware.

Here is step by step the procedure:
1. boot into bootloader( Vol Down + Power button with phone plugged to PC)

2. Download fastboot.zip from here: https://mega.co.nz/#!fZ4CCDJD!gSMMZG...l3Ro6kv7Rpz-40

3. You need to flash Boot and Recovery image in fastboot..Click thru the folder till sub folder named Fastboot..Press Shift+Right Click - Open Command window here: type - fastboot flash boot boot.img, press Enter..next command - fastboot flash recovery recovery.img..with this you have flashed boot and recovery images..dont close the command window and dont unplug your phone..stay connected

4. prepare you SD card, i used San Disk 64GB, any card 4GB+ should do the trick..Card must be formated in FAT32 otherwise your phone wont recognize your card..this you can do very easy way..
This small utility will help you: http://download.cnet.com/EaseUS-Part...dlPid=10982635

5. download the rollback package for M7 TL-10 http://consumer.huawei.com/it/suppor...x.htm?id=45463
copy dload folder to your formatted FAT32 SD Card....remember, you are still in bootload mode.

6.now go back to opened command window, and you type: fastboot reboot and press enter..the card is till not inserted.the phone will restart and now you can unplug your phone..you will get scree restart/wipe data/wipe cache

7.insert your SD card into your phone, press and hold Vol UP and Down at the same time and press Power button. phone will restart but you are still holding Vol Up and Down pressed for aprox. 10 seconds till Huawei logo disappears.

8.Update will start automatically , when update is done, phone will restart again till screen restart/wipe data/cache..you have successfully rolled back..stay there, do nothing, leave your phone how it is.

9.download stock Rom, i chose this one: http://consumer.huawei.com/it/suppor...x.htm?id=45462

10.remove your SD card, and on PC/Laptop delete the previous rollback update.app, but dont format the SD card..now copy dload folder from downloaded firmware, in this case B125SP02..
insert you card back into your phone

11.Now press again Vol Up+Down, keep pressing for aprox. 10 seconds and restart the phone with one Power button press..wait until the Huawei logo disappears..update will start automatically...wait till its finish, phone will restart and boot your system. And you are back again.

I guess, this quide should help also for TL-09 model, but with with Rom for your model.

Hope i could help you. If you have any questions, just PM me.

mediapad x1 softbrick

i have mediapad x1 .when try to install kitkat 4.4.2 from cwm recovery fastboot stopped just black screen no power on just light red and green:

please help me.