yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] darkspr1te:
Hi,

I need to think on this, there is a solution, i cant 100% remeber, have you tried the firmware 900lang? i think there was a .tar version that could be flash via odin.

here is uh24, i often went back to this during issue's, some version of the scripts clear certain sections of the system not normaly cleared out when updating.

UH24 SHV-E160L Only

Here is TWRP for the same TWRP SHV-E160L

You also should check if adb is coming on when you try recovery mode/normal boot, it's important to know if it is, it shows when in the init script the hang is happening,

To refresh the recovery mode /download mode procedure that never failed for me.

1. remove usb+battery, replace battery

2.hold vol up+home then press power untill vibe, release power.

3.release vol/home when recovery starts

Other possible solutions is writing a recovery image to the boot partition, i did this often while working on partitions and recovery development, it ment i did not have to hold the recovery buttons every time, i forgot often and just rebooted, then had to hold 'sigh' reset etc. this will allow certain hacks to take place in terms of resting your system to clean using adb

linux will be useful if not required for this type of work.

XDA have posted of some linux distributions that are prebuilt with the tools to work on roms/images , there are also guides on creating .tar files for oding flashing

a quick example is unzip the .img file from the update, in the case of twrp you want recovery.img, rename it boot.img and use .tar maker one click

you should have a odin flashable .tar file with recovery name boot so it gets flashed to boot, you flash it in the normal way, no changes from any of the normal guides, no exotic extra ticks in the left panel other than the normal ones you use

I would discuss this route further here before taking it, i generalized a lot of that.

EDIT:Question, have you tried both twrp and vanilla recoveries ?

darkspr1te
[AT&T Samsung Galaxy Note I717] KalBha:
Hi,

Thank you for your quick reply. I haven't tried the 900 lang firmware.

Still downloading the ROM from the link sent by you.

You also should check if adb is coming on when you try recovery mode/normal boot, it's important to know if it is, it shows when in the init script the hang is happening. I am not aware how to do this, but going through the adb tutorials in xda.

To refresh the recovery mode /download mode procedure that never failed for me.

1. remove usb+battery, replace battery

2.hold vol up+home then press power untill vibe, release power.

3.release vol/home when recovery starts

I was doing this all the time, but it isn't working. The mobile gets stuck at the Samsung logo.

I don't know much about adb but used it few times based on the instructions. I used only twrp recovery and it worked for me before this boot loop. I didn't try vanilla recovery. I tried CWM recovery, even this worked for me earlier but not now. I converted the recovery.img from twrp from your link to boot.img and changed it to .tar file and flashed it through ODIN but the phone is still stuck in boot screen.

I will flash the ROM after completion of download, and let you know the status. Meanwhile going through adb tutorials to make the phone ready for a clean installation. Any suggestions from your end will be of great help.

I downloaded SHV-E160L(4.0.4)HOME_E160L.UH24.1821_CL966093_REV02_user_low_ship(MMUG).tar.md5.zip. I unzipped it and when i tried to call it in ODIN, it says "MD5 hash value is invalid". So I removed .md5 at the end and flashed it as a .tar file. I may be wrong doing this way. Finally the result is same. The phone rebooted and the computer says MTP USB device driver installation failed. Need your help to make my phone up again.
[AT&T Samsung Galaxy Note I717] Bruez:
Xiaomi Hongmi 1s

Hi All,

It looks like I corrupted the bootloader on my Xiaomi Hongmi 1s. I have tried to use the same method as above, but I have the same result in QPST:

I think I have to "hack" the hardware the same way, but anybody knows how to do it?

Thanks!

Zsolt
[AT&T Samsung Galaxy Note I717] ertioct:
I have the exaclty same problem with a K910 qualcomm in sahara memory dump mode. I am totally desperated, if anybody knows how to get out of a locked bootloader or this damaged mode, please show me what are test points to enter qualcomm emergency mode.

Thank you
[AT&T Samsung Galaxy Note I717] JastaPein:
Help please !!!

i would like to know if i still can revive my soft brick korean note (SHV E160L)

what happened is i rooted my phone but it doesnt give me any root access.

so, i decided to do a factory reset in settings under backup & reset and when my phone

reboot, it doesnt booting normally. it only shows the U+ LTE Logo then after a couple of

seconds it reboots again & again & again.

i tried to flash the stock ICS UH24 but no luck.

i tried to flash the stock ICS UH24 + PIT File that ive got (checked all auto reboot, repartition & f reset) here but still no luck.

i did this using ODIN and it always showing me a SUCCESS but my phone still stuck in bootloop.

i need someone who can help me with this :( i am willing to donate via paypal just to fix this phone..
[AT&T Samsung Galaxy Note I717] mickeyasamoah:
I have a quick question. Does this thread give guidelines on how to unbrick HTC devices??
[AT&T Samsung Galaxy Note I717] tech128:
Yes it does. Most HTC devices are based on qualcomm chipsets, which the same is true of samsung.

Reading this thread and the one linked in the op's post won't give you a full understanding, but it will definitely give you a lot of info on how the process works.

Basically you need to get into qdloader mode somehow.

Sometimes this can be easy, other times it will be hard.

Next, you need a hex programmer that will work for your qualcomm chipset.

You also need a msimage.mbn file, which has to be created with qpst tools somehow.

Once you are in qdloader mode, you send the hex programmer and the msimage.mbn to the phone and the phone should enumerate as a mass storage device.

Once you get to that point, you just need to rewrite the partition table and rewrite the bootloaders so you can get back to odin or fastboot and reflash the phone.

That's the basic gist of it.

I don't think this method works for secboot3 because the main problem is that the hex programmer has to be signed specifically for each device.

There's still a LOT I don't understand and am trying to figure out.

I've created a wiki page for debricking qualcomm chipsets on the xda wiki.

http://xdaforums.com/wiki/Qualcomm_chipsets_-_Secboot2

darkspr1te, when you get a little time, do you think you can post all of what you have on debricking to the wiki?

Don't be concerned about formatting, etc.

We'll all help to format the info and polish it.

I think that would be a great addition to the debricking community if we could all help to pool what we know about debricking and create a useful guide.
[AT&T Samsung Galaxy Note I717] awefeasdf:
help with debrick

Hey darksprite! I hard bricked my sgh-t989 today. I think it has the same or similar chipset as the shv-e160: Qualcomm APQ8060 Snapdragon. I tried using your tool, but I have a few problems. First, your readme says to use ./brickfix, but there is no such file so I used ./brixfix.sh. When I did that, it asked me if I wanted to flash, I pressed 'y'. It had a lot of writing/response messages. Then I got this:

Writing 1024 bytes to 0x000b8000; 866884 bytes left.
Invalid Response: 0e 57 72 69 74 65 20 75 6e 73 75 63 63 65 73 73 66 75 6c 0a

If HEX/MBN uploaded correctly, please allow for short delay and re-run brixfix to continue the debricking session, a screen showing device options may appear, close this new screen

Rerunning produces the same result produces:

Executing qdload
Requesting SoftwareVersion...
Invalid Response: 0e 49 6e 76 61 6c 69 64 20 43 6f 6d 6d 61 6e 64 0a
Failed to get software version

Please help. If you are wondering how I bricked it, the app Swapper 2 did it. :crying::crying::crying::crying:
[AT&T Samsung Galaxy Note I717] awesomegabriels:
will this work for me

i mistakenly flashed my at$t galaxy note with a galaxy s3 rom. N0w all am left with is the inevitable black screen please can this work for me and how.remember my phone does not show any signs of power even when connected to a pc nothing happens just the black screen
[AT&T Samsung Galaxy Note I717] darkspr1te:
Did you read any info about which hex to use, correct bootloaders?
[AT&T Samsung Galaxy Note I717] darkspr1te:
You will either have to jtag the device to get out of the boot loop or open it and find the boot_cfg resistor , see my shv-e160 thread on how to work it out. Its not noob friendly, sorry but that just the way it is.
[AT&T Samsung Galaxy Note I717] tech128:
Yes it should work for you. You have to remember though, if you don't get anything from the pc, that means you aren't even getting qdloader mode. You need to get to qdloader mode to do anything.

You'll need to open the phone and find which pins to short to cause the phone to enter qdloader mode.

That's the hard part.

If no one else has figured that out before, then it's up to you to do so.

You'll have to read datasheets on the msm8660 to find out which pins to short.

That can be particularly dangerous though, since shorting the wrong ones can permanently brick the motherboard beyond repair.

darkspr1te found them on his because he was willing to take that chance.
[AT&T Samsung Galaxy Note I717] awefeasdf:
Not sure what you mean by that, but being the impatient person I am, I twiddled with the sh file, and after commenting the thing about flashing boot.img, I got through it no errors. I then reran, did pressed y to all the new options, reboot...and no connection to pc whatsoever. Looks like i'll have to send it in for JTAG. :(
[AT&T Samsung Galaxy Note I717] Krebs830:
Hi! Using Brixfix, a stock JB ROM, a lot of research and a little trial and error I was able to unbrick my Galaxy S2 (SGH-T989, 16GB) from the Qualcomm 9008 mode. I used the latest Ubuntu, but for some reason the "read" commands in Brixfix.sh didn't work, so I bypassed those parts. I also took a chance and used the partition0.bin from the folder you supplied (since they're similar chipsets and both are 16GB) and it worked. Afterwards, I was able to boot it into Odin mode and reload the stock .pit and ROM, and now the phone works like it should. Thanks!

Edit: I uploaded the files I used to www.sendspace.com/file/gy3s0l (lowercase L).
[AT&T Samsung Galaxy Note I717] venkateswara:
Need help to unbrick zte nubia z5s mini

Respected Sir,

I did like this...

( I am responsible for whatever the happens, I want to take risk, so please kindly help me sir)

1. I visit the page: nubiamobileshop.com/nubia-z5s-mini-4-7-inch-hd-screen-ram-2gb-qualcomm-android-smart-phone , there i saw downloads option, a newer version. ( Now i realized that one does not have 's' so both rom may be different).

2. downloaded that update file to pc.

3. I took clockworkmode backup. ( i have this in my pc now)

4. I installed cwm recovery file (as this supports english language). cwm file name:RecoveryInstallerfornubiaz5sminionly.apk link: firedrive.com/file/5A6410A0B5158865

5. Using this apk, I reverst back , stock rom recovery instead of custom rom recovery.

6. I tried to install the update.zip using stock rom recovery , but it says

assert(getprop"....") failed. installation aborded.

7. So i deleted the that line using notepad in update.zip by following the path

D:\update\META-INF\com\google\android\updater-script .

8. I tried to install that update.zip using stock rom. It again installation aborded.

9. Then i installed cwm recovery and rebooting into cwm recovery mode , I installed that update.zip.

It was installed.

After installation it says "do you want to disable stock recovery", I choose NO option.

after that , it again asks, you want to keep root , I choose Yes, I want to keep root.

10. I choose reboot option to reboot the phone.

But the phone doesn't swich on... Thats it...

When I connect to mobile to Phone It shows

"HS-USB diagnosis mode 9008" COM port 42 driver installed.

11. By googling, I downloaded the files , QPST-2.7.399 .

12. Open " QPST Configuration " and choosen COM port:

see. fig. 1. link: facebook.com/photo.php?fbid=584452891672403&set=pcb.584452935005732&type=1&theater

13. Open " eMMC software Download app" . Choosen options according in the fig. 2.

see fig. 2. link:facebook.com/photo.php?fbid=584452888339070&set=pcb.584452935005732&type=1&theater

14. I don't have profer "flash programmer file name " and "boot image" for the zte nubia z5s mini. I mean MPRG8064.Hex and 8064_msimage.mbn files.

This is what I tried. Please help me. I will be great thankful to you sir.

Thank you.
[AT&T Samsung Galaxy Note I717] paranoxxx:
Hi ,

i think it did not worked for me .

The first time i run the brixfix.sh it seemed that it was working , there was informations of writing files...

but there was a mistake , the Qualcomm .bin and .mbn files for the T989 were not in the brixfix folder

now when i try to run brixfix.sh , i have this :

Tested with backtrack r5 :

Brick Fix v2-0
______________
By Darkspr1te, See README for thanks & References

Checking For Qualcomm Device
No QDLOAD device found, checking for SD-CARD Mode
Device found !!!!
Mode is SD-CARD/msimage mode at device node /dev
With USB PID/VID ID of 05c6:9025
Detailed Output is Bus 001 Device 015: ID 05c6:9025 Qualcomm, Inc.

Do you wish to write parititon Warning Dangerous
y

Writing parititon to /dev
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory

Do you wish to write bootloaders Warning Dangerous
y

Writing bootloaders sbl1,sbl2,sbl3,rpm,aboot to /dev
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory

Do you wish to write TrustZone Warning Dangerous
y

Writing TrustZone to /dev/
dd: opening `/dev': Is a directory

If no errors occured then disconnect and remove/replace battery, if ANY error occured do not disconnect device, fix error and rerun or seek advice !!

same on ubuntu :

paranox@ubuntu:~/Desktop/Brixfix-2-1/Brixfix-2-1$ sudo ./brixfix.sh

Brick Fix v2-0
______________
By Darkspr1te, See README for thanks & References

Checking For Qualcomm Device
No QDLOAD device found, checking for SD-CARD Mode
Device found !!!!
Mode is SD-CARD/msimage mode at device node /dev
With USB PID/VID ID of 05c6:9025
Detailed Output is Bus 001 Device 013: ID 05c6:9025 Qualcomm, Inc.

Do you wish to write parititon Warning Dangerous
y
Writing parititon to /dev
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory

Do you wish to write bootloaders Warning Dangerous
y
Writing bootloaders sbl1,sbl2,sbl3,rpm,aboot to /dev
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory

Do you wish to write TrustZone Warning Dangerous
y
Writing TrustZone to /dev/
dd: opening `/dev': Is a directory

If no errors occured then disconnect and remove/replace battery, if ANY error occured do not disconnect device, fix error and rerun or seek advice !!
paranox@ubuntu:~/Desktop/Brixfix-2-1/Brixfix-2-1$

i'm using it for my t989
[AT&T Samsung Galaxy Note I717] darkspr1te:
The script is not finding the device in sd-card mode , see the bold section, your ment to see something like /dev/sdb or similar.

The script can be run in three sections, you can load the hex, then the sdcard files and finally write partition/bootloaders,

I suggest confirm the device is booting to sd-card mode , check using 'dmesg' command

$ dmesg
[AT&T Samsung Galaxy Note I717] darkspr1te:
Sadly no one has posted their files yet. I worked on windows backup first as i figured most users would be windows.
[AT&T Samsung Galaxy Note I717] awesomefireduck:
I do have a TWRP backup of my note e160L 32GB on my PC (made a backup of entire SD to pc including TWRP folder...)

Could that be of any help?
[AT&T Samsung Galaxy Note I717] SouL Shadow:
That will only be useful AFTER restoring your phone to a working state. However, the files needed to restore the boot chain are NOT included in a twrp backup. Typically most of the files needed are found in an official firmware update from your carrier/manufacturer. For HTC devices these files are found in an RUU. Not sure how Samsung distributes updates.

In some RARE cases you will also need some additional files ONLY AVAILABLE from a working device. This case is more RARE and only needed if your entire emmc flash was wiped or corrupted. These files (usually entire partitions) hold the device calibration data and NV items and other info such as Model Number, IMEI/MEID, etc... Again, these files/partitions are only needed in RARE cases and will often require some custom reconfiguration done by hand.
[AT&T Samsung Galaxy Note I717] darkspr1te:
As mentioned by SouL Shadow mentioned TWRP does not produce backups of partitions, boot loaders and other vital parts. My backup program is only designed to get the basics for booting the phone, Samsung does not include these in updates all the time, only sometimes, I actually used i717 loaders to create the first model of debrick, then manually created backups of the required files from a full copy of the emmc image which I did the moment I get it too boot the first time, then I created a new partition table by hand, Unix does not format the emmc when it does partition table work so I could then access each partition by using dd and the skip/count parameter. I do data recovery as a trade so that was not so hard, swapping between sectors/bytes/cylinders has to be monitored very close, E:V:A's work in partitions, headers of .mbn files allowed be to have some prior knowledge the start of the data I was looking for, the skyrocket partition table gave me the sizes of the files I needed to recover. Sadly doing this via any remote method is next to impossible.

These tools are also to provide Devs facilities to study further the structures and layouts used by Samsung(other devices are supported to some degree)

Data collected here will be studied and reposted back to the community via threads like E:V:A's partition thread. Automated debricking as well, certain parts of Samsung are always the same so the more we see the more we rebuild without needing files from Samsung.

Samsung should have had these debrick tools available from the get go, the security is there and would not harm the security of devices by having them available to the public.

sent from the Darkspr1te's lair
[AT&T Samsung Galaxy Note I717] darkspr1te:
I am still getting a lot of PM's for help debricking devices, sadly I can't help these people as I don't have the correct backups for them. I am asking shv-e160x users to please GOTO my first post, download then brixfix with python, run the backup.bat program to create a debrick package for their device and then zip/upload to send space and post the URL/link here, I can't help these users without readers giving back, it is too time consuming to do each debrick one by one which is why I created the backup.bat for windows users.

sent from the Darkspr1te's lair
[AT&T Samsung Galaxy Note I717] sjravi:
Can this method be implemented for S3 I747?
[AT&T Samsung Galaxy Note I717] darkspr1te:
It's possible, I would have to study the partition table/allocations of loaders. The pit file helps there a great deal.

Root is required to get the backups

I am not a i747 user so I am not sure which CPU it has, if it's Qualcomm I can help, if it's anything else then I would be very blind on how it's played out.

sent from the Darkspr1te's lair
[AT&T Samsung Galaxy Note I717] sjravi:
Its a 8960

I have the partition table, pit file and images of all the partitions.

Its in this state cause I flashed T999(tmobile S3) images on this device so it fails to load SBL1. I did not touch the partition table and pit.

Pit and partition table attached
[AT&T Samsung Galaxy Note I717] darkspr1te:
MSM8960, we do have the required .HEX and msimage.mbn need to get the device into sd-card mode but so far no one has actually got it to work, if you want to try this step for yourself you will need linux,

download

https://github.com/jcsullins/qdloader

and

http://www.sendspace.com/file/dk7hnt

put qdload.pl and the .hex/.mbn file into a folder and then execute

perl qdload.pl -pfile MPRG8960.hex -lfile 8960_msimage.mbn -lreset

if your device re-enumerates as a sd-card the your half way there,

once in sd-card mode find the correct device address using dmesg, in my example it's SDB

so you would then do a backup of the entire device,

dd if=/dev/sdb of=/home/usersname/devicebackup.bin

from there we can then rebuild the system provided we can get copies of the sbX/tz/rpm/aboot files (some will be ok on your device, others may be damaged)
[AT&T Samsung Galaxy Note I717] SouL Shadow:
Sadly, for the 8960 devices, if security (root cert checking) is enabled by the OEM (htc, samsung) it appears that we will need a signed hex. Another user showed me a dump of the pbl and there is security checking on the hex if the qfuse is blown. Unless we can find a way around this, we will need a signed hex from each OEM.

-SLS-
[AT&T Samsung Galaxy Note I717] darkspr1te:
Thats going to make things hard for us that want to repair our phones :(
[AT&T Samsung Galaxy Note I717] awesomefireduck:
Koxda

I posted this yesterday to koxda.com (chinese phone forum with roms for lots of korean models, not just e160*)

This is the post: http://koxda.com/thread-109476-1-1.html

If anyone has suggestions concerning the translation(especially technical terms), please send me a messege/reply. ;)
[AT&T Samsung Galaxy Note I717] darkspr1te:
Its annoying that despite the number of people I've helped debrick their devices, non have yet to post the 32gb partition, it does not even have to come from a L model a S/K partition will work.(pit file though has to come from a 32gb L) I still don't have the aboot.mbn/pit/partition for K/S models so if they do end up bricking, they will come to me and I can't help them, not because I don't want too but because the files I needed cannot be recovered after the brick without major work involved, work I don't have time to do.

That's why I wrote the backup.bat programming for windows, it does backup the correct files so we can debrick later.

sent from the Darkspr1te's lair
[AT&T Samsung Galaxy Note I717] BarakOsama:
Pit file please..

Please someone share a PIT file of 32GB E160x device.. :(
[AT&T Samsung Galaxy Note I717] maestrobarako:
i think that there are only few who has a 32Gb e160x device as most of us have the 16GB.. and maybe if there are some, they maybe are too noobish and afraid to make a back.up or give a pit/partition file..
[AT&T Samsung Galaxy Note I717] awesomefireduck:
Tutorial

I made a tutorial for making the backup.

please correct me if anything is wrong, but I didn't exactly had a phone to try it out...

Again, at koxda...

http://koxda.com/forum.php?mod=viewthread&tid=109729&page=1

Please feel free to use the pictures here or elsewhere.