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

Sorry but it's been a very busy time for me, my business peaks at this time of the year, plus other stuff going on.

I've been working on a recovery system from the ground up. what i though was a simple procedure do alter the init.d of the recovery boot turned out to be a real exercise and i in the end put it down for the xmas period. As to why the thread is slow, I've yet to publish my new findings, a lot has come forward since, new info which changes things.

What time zone are you in ?

It might be quicker if we chat on irc. pm me and i will arrange a irc meeting

Oh can you get hold of a pit file for your device too or can some one post the pit file,

to copy it would be

adb shell su -c "dd if=/dev/block/mmcblk0p11 of=/sdcard/'modelnumber'.pit "
adb pull /sdcard'modelnumber'.pit

post the downloaded pit. I have the bootloaders, cwm, partiton table but no pit.

darkspr1ite
[AT&T Samsung Galaxy Note I717] darkspr1te:
Great news those who are following this thread, Today I achieved boot from sd-card.

Currently using the 8660_msimage.mbn file as the boot source. what does this mean to you. Well if your device is a msm8660 and your device is in emergency dload or ehost dload or QDL mode then a simple image file placed onto your removable sd-card will bring it alive again. Further work need to be done to repair the device but this skips a step, currently we have to use qpst in windows to load the image onto the device, now i have a working image that i can use on a sd-card and boots your phone, Bonus is, it shows all sd-cards including your external!!!

here is dmesg output

[ 8447.574034] scsi16 : usb-storage 1-2:1.20
[ 8448.572797] scsi 16:0:0:0: Direct-Access Qualcomm MMC Storage 2.31 PQ: 0 ANSI: 2
[ 8448.573163] scsi 16:0:0:1: Direct-Access Qualcomm MMC Storage 2.31 PQ: 0 ANSI: 2
[ 8448.573989] sd 16:0:0:0: Attached scsi generic sg3 type 0
[ 8448.574698] sd 16:0:0:1: Attached scsi generic sg4 type 0
[ 8448.579116] sd 16:0:0:0: [sdc] 30777344 512-byte logical blocks: (15.7 GB/14.6 GiB)
[ 8448.579862] sd 16:0:0:1: [sdd] 3911680 512-byte logical blocks: (2.00 GB/1.86 GiB)
[ 8448.580403] sd 16:0:0:0: [sdc] Write Protect is off
[ 8448.580408] sd 16:0:0:0: [sdc] Mode Sense: 0f 0e 00 00
[ 8448.581029] sd 16:0:0:1: [sdd] Write Protect is off
[ 8448.581034] sd 16:0:0:1: [sdd] Mode Sense: 0f 0e 00 00
[ 8448.581524] sd 16:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 8448.582156] sd 16:0:0:1: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 8448.592525] sdc: sdc1 sdc2 sdc3 sdc4 < sdc5 sdc6 sdc7 >
[ 8448.595025] sdd: sdd1 sdd2 sdd3 sdd4 < sdd5 sdd6 sdd7 >
[ 8448.598795] sd 16:0:0:0: [sdc] Attached SCSI removable disk
[ 8448.601154] sd 16:0:0:1: [sdd] Attached SCSI removable disk
darkspr1te@darkspr1te:~/Desktop/partition_load_pt/test$

And lsusb

Bus 001 Device 037: ID 05c6:9025 Qualcomm, Inc.

this also could mean the possibility of dual boot.

i've not started work on dual yet, this will happen much later, right now i need to now see if the samsung bootloaders will work off sdcard

darkspr1te
[AT&T Samsung Galaxy Note I717] unoaman:
Thats a great news..
[AT&T Samsung Galaxy Note I717] darkspr1te:
Hi All,

Ok ive attached the dd image of the sd-card, to use just

dd if=8660_msimage.bin of=/dev/'pathtosdcard'

pathtosdcard you swap for the linux dev location of your sd-card, sdc/sdd etc. if you dont understand then dont use this file.

Now if anyone who is in edload or emergency dload or qdload or qdl mode please try this on a sd-card in your device and report back. i need the feedback to continue the research.

darkspr1te

attachment removed, due to it not working bwana.
[AT&T Samsung Galaxy Note I717] RussianBear:
Great job, dark! I've posted in the sensation unbrick thread. You might want to see if people on galaxy s2, og note might be interested in checking this for you.
[AT&T Samsung Galaxy Note I717] sinner99:
so I've a question for ya ...very nice thread btw...you're a pretty smart guy! few weeks ago..i was typing way too fast dd;'ing my recovery in..i've done it literally a thousand times but for some reason this time i imaged via dd my recovery to mmcblk0p4 1KB (unnamed partition with '55 AA' MBR signature)... :( anyway to simply turn that around only? i got no boot. no post. nothing. plugged into my linux box..its ubuntu 12.0.4.1 server so terminal only...i dont see it anywhere via blkid...ill try lsmod to see what hardware i can see i should be able to spot it. I just seem to lose the steps you take and they are important ones..i have gotten as far as generating a 8660_whatchamacallit file..lol got allt hose necessary sbl1,2,3, tz, rpm etc. qpst in windows does not see the phone. i got lost somewhere in your steps basically cause you're way smarter then me and I'm not u nderstanding the description so well. this phone i have on a 3 y r contract nearly a year in..and the provider and kiosk i bought it at basically told me to take a hike. :( i replaced the screen with a bricked notes screen while back and it takes the back plate with the imei sticker with it...no idea where that bricked phone came from but i did not want its imei and serial dispplayed even though they did not reflect the hardware id's because they remained what they were. any help you can give its hugely appreciated. ::

edit: ****..shoulda come to the last page...mines an i717m bell device..this will work for me will it? wow nice if it does!
[AT&T Samsung Galaxy Note I717] darkspr1te:
Hi,

Ok it's possible it could work, does the device show up in linux under lsusb ? if it does not then this trick wont work yet as your device is crashing in the boot stage. you would have to find a specific resistor on the board, short it too ground to trigger the emergency boot and that would allow access to qpst to flash a new EBR (Extended boot record or mmcblk0p4 )

My sdcard trick has problems, it's not working all the time, only 1 in 10, i dont yet know why.

darkspr1te
[AT&T Samsung Galaxy Note I717] SouL Shadow:
Sinner99:

When you plug the phone in to the linux box, what shows up for: dmesg | tail -15

-SLS-
[AT&T Samsung Galaxy Note I717] sinner99:
no it doesnt appear in lsusb...unless its integrated circuit solution, which i doubt. which resistor? i only have a 301k jig which does nothing for me. :(
[AT&T Samsung Galaxy Note I717] darkspr1te:
Then your only choice is the wire mod or jtag. if you never done electronics, soldering and such, go jtag. if you can solder, goto start of this thread, you will see how i found the boot resistor. the boot resistor is a tiny smd near the cpu, it's not a recommended solution for anyone who's not been doing electronic soldering for a few years at least.

darkspr1te
[AT&T Samsung Galaxy Note I717] SouL Shadow:
1) Plug in to wall charger for about an hour.

2) If it has a removable battery, pull it out, put it back in.

3) connect to pc

4) hold power button to turn phone on

5) as root run: dmesg | tail -15

Post a reply with that output.

I'm looking to see if it connects with a tty

(Fyi: battery charging from a bricked state will not show the LED, but will charge)

-SLS-
[AT&T Samsung Galaxy Note I717] sinner99:
ok, thanks...i havent done the charge yet..altho the battery is full..its had alot of being plugged in to pc and wall. regardless here is my current output of dmesg | tail -15

[334448.103349] sd 14:0:0:2: [sdj] Write Protect is off

[334448.103356] sd 14:0:0:2: [sdj] Mode Sense: 4b 00 00 08

[334448.104482] sd 14:0:0:2: [sdj] No Caching mode page present

[334448.107837] sd 14:0:0:2: [sdj] Assuming drive cache: write through

[334448.114596] sd 14:0:0:2: [sdj] No Caching mode page present

[334448.118645] sd 14:0:0:2: [sdj] Assuming drive cache: write through

[334448.125113] sdj: sdj1

[334466.010125] sdj: detected capacity change from 1977614336 to 0

[346330.080018] EXT4-fs (dm-4): error count: 3

[346330.080026] EXT4-fs (dm-4): initial error at 1356551381: ext4_journal_start_sb:371

[346330.080033] EXT4-fs (dm-4): last error at 1356775348: ext4_put_super:887

whats really weird....blkid does not list sdj at all...sdj was my sdcard when i dd imaged with it plugged direct to the linux box. now its in my phone plugged to the linux box and it does see it eh?! it appears there is some sort of life here...:D

dark! yes i shall check your instructions for fixing the boot problem. I still cant believe bell service provider opened phone seen imei label removed(i replaced the glass, the label comes on the chassis with it, so it was from another phone, but still same imei hardware wise)and boxed it back up and shipped it back. on dec 27. merry xmas to you asshats too eh?! lol i'll get this figured thanks alot to you fellas. thanks man!

edit: looking at the output again...i guess it doesnt mean nothing. it appears what it is...i had the card in pc...wrote an image to it, and removed it. size change reason. duh. lol
[AT&T Samsung Galaxy Note I717] SouL Shadow:
Not seeing _anything_ listing there. Try wall charging, battery pull, then connect to pc and dmesg | tail -30

(Longer dmesg output to compare with previous)

-SLS-
[AT&T Samsung Galaxy Note I717] sinner99:
edit2: dmesg | tail -15 had nothing regarding the phone being plugged in at all. :(
[AT&T Samsung Galaxy Note I717] SouL Shadow:
If you can't establish any connection via usb, then there's probably a hardware problem and little hope for a software fix.

These qualcomm chipsets are designed to establish a usb connection even if the nand/emmc flash is blank.

-SLS-
[AT&T Samsung Galaxy Note I717] darkspr1te:
It may be possible that he is stuck in sbl1/sbl2 as the phone does not enumerate as usb device until sbl3 is loaded.

But without knowing the boot resistor for the device ( we maybe be able to work it out with hi-res shots of main board) we cannot get it to boot over to fail mode(ehost or qdload mode) (pid 9008/90025).

darkspr1te

p.s my guide is not that good, i was learning the device at the time and never done this kind of work before so it's disjointed, i will update it one day.
[AT&T Samsung Galaxy Note I717] SouL Shadow:
Any pbl/sbl establishes a usb connection. The best case would be for it to enumerate the partitions, worst case would just be a usb serial ttyUSB. That's why I laid out those instructions. As long as the hardware works and the device has power there should be some type of connection.

Well, you already voided your warranty by opening the device (that's the real reason they sent it back, unauthorized user repair). So, if you're up for the task, open it up again, make sure they didn't disconnect or break something inside. And make sure you've wall charged the battery. In this state it doesn't draw enough power over a pc usb link to charge up the battery.

-SLS-
[AT&T Samsung Galaxy Note I717] coffeeaddictako:
My Phone Bricked!

Hello...actually i really don't know what to do with my phone...it got bricked when i flashed a new rom and something was wrong with it so i decided to change some codes on the build prop (silly me)...and the sd card got corrupted and because i didn't know what to do i pulled out the battery (silly me again) and it didn't turn on, i brought it to the repair shop and they tried to jtag it but nothing happens, they even told me that there's nothing i can do about it and i should just throw it away...my computer can detect it as Qualcomm HS-USB QDloader9008 and in qpst as Q/QCP-XXX(Download)... i can't follow darkspr1te method bcoz i can't access eMMC Software DL...hope someone can help me...i am not that good with some of the stuffs i have read here....thanks in advance..
[AT&T Samsung Galaxy Note I717] coffeeaddictako:
forgot to mention... my phone is SHV-E160k...
[AT&T Samsung Galaxy Note I717] sinner99:
well here is a hi res shot of my board anyway....im comfortable soldering i just need to know exactly what im going after and what I'm doing. i guess i got a good read ahead of me eh? lol will the $50 jtag fix work for my problem though is the question of the month!

there are some solutioins that are free for your problem...I've had this qhsusb-dload issue with other phones, as i recall it wasn't tough to fix. search real good. googles your friend. I had too look extra special for that i do remember, but its out there. I'll check my bookmarks. i seriously wish i was in your position rather then mine :(
[AT&T Samsung Galaxy Note I717] darkspr1te:
Hi,

If you disconnect the flat connectors around the board and the 3 or 4 screws you should be able to remove the main board.

if your main board looks like the one in the post

http://xdaforums.com/showpost.php?p=33715333&postcount=98

then chances are we have gold as there is a resistor on main board that has to be grounded only when you plug it in, from there qpst takes over.

if you look at the last shot i have a wire coming from the resistor near the cpu, the wire is connected to the low side (solder point away from cpu not the solder point near cpu).

that is the boot order resistor, if it's 1 the system boots emmc , if it's 0 the system does emergency boot sdc3.

I had forgotten yours was a i717, i only noticed when i saw the jtag point is unpopulated (to right of gray wifi cable and left of the screw)

so next step, remove screws and flip board around.

here are some videos showing assembly/disassembly/resistor operation

http://www.youtube.com/watch?v=BLDqtNaK7tY

http://www.youtube.com/watch?v=voldEx30vM0

Now refer back to your images, there are 3 flat idc type cables at the top of the image, the two on the most right of the image(or bottom if phone is upright) must remain connected for usb, i normally leave all 3 connected and unclip the rest, then the two parts should open like a book, sort of. anyway when the low side of the resistor is grounded and you plug in usb, system boots in QPST mode, bypassing any currupt bootloaders allowing you to rewrite new via the sd-card mode. soon this wont be needed as i've been attempting to get the device to boot off sd-card.

once in qpst mode you use emmcswdownload and the files i've posted to write a sd-card mode bootloader to your phone, then you backup your entire phone from linux. from there we need access to another device (i717 ) to backup the partition and bootloaders, i happen to have i717 bootloaders but no partition backup (yet)

i am working on a program to build the partition without qualcomm tools, i just need a working i717 to run a program on.

darkspr1te
[AT&T Samsung Galaxy Note I717] nathanlewan:
QDL Mode

First of all let me say THANK YOU for all your hard work. I have found this thread wonderfully informative. I grasp all the concepts, but I have hit a roadblock early on, and was hoping i'm just doing something silly.

I have a AT&T Galaxy s3 I747

I flashed a I9300 kernel on it.... oops.. I am dumb. Now I am learning all these techniques to fix it ( maybe a blessing in disguise)

As you may have guessed, black screen, won't turn on, button combinations do nothing, etc.

I am running Debian Wheezy, which hosts virtualbox running Win7x64

When I plug my phone into my computer, debian picks up on it right away:

lsusb:

Bus 002 Device 066: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

dmesg:

[270024.486390] usb 2-1.8: new high-speed USB device number 66 using ehci_hcd
[270024.579110] usb 2-1.8: New USB device found, idVendor=05c6, idProduct=9008
[270024.579114] usb 2-1.8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[270024.579116] usb 2-1.8: Product: QHSUSB_DLOAD
[270024.579117] usb 2-1.8: Manufacturer: Qualcomm CDMA Technologies MSM
[270024.579405] qcserial 2-1.8:1.0: Qualcomm USB modem converter detected
[270024.579463] usb 2-1.8: Qualcomm USB modem converter now attached to ttyUSB0
[270028.110574] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0

I then pop over to VirtualBox, and make the Qualcomm USB device available to the win7 VM. Device manager picks up on it, and I tell it to install using the QHUSBx64 drivers I downloaded from XDA. Then the device shows up in device manager under PORTS, with the label "Qualcomm HS-USB QDloader 9008 (COM3). It has a yellow triangle next to it, and the device manager reports a code 10 error, stating the device can't start.

I can't for the life of me get that installed correctly. I have searched everywhere but every QHUSBx64(tried 32 as well) driver I find is exactly the same, and won't fully work for me. QPST will not communicate with the device at all, and i'm assuming it's because of the error shown in device manager.

I feel like if I could figure that out, I would be ok moving forward, but many searches have gleaned nothing on this initial step for this un-bricking process you have so nicely created here.

Any help would be greatly appreciated.
[AT&T Samsung Galaxy Note I717] saketh91:
will this work on any device with msm8960(i mean my at&t htc one x)
[AT&T Samsung Galaxy Note I717] SouL Shadow:
Oh, nice! I'll have to check that out. I have a c++ version in the works. With limited free time it's progressed slowly, but I'm almost done with the hdlc framework. I tried using some of the Gobi code, but they only implement a small subset of commands and it does not lend itself to being extended, so I had to scrap that and start from scratch. I'm hoping to have a very basic working test version before the weekend is over.

Could you add that to my qdl thread, without the device specific files, and include a description of what it does and how it works, along with links to the author's work (if there are any)?

I considered writing a bash version, but working with the data/commands in hex is difficult in bash. Plus the array support in bash is very basic. It would have been a lot harder to process the raw input/output.

-SLS-
[AT&T Samsung Galaxy Note I717] saketh91:
exactly the same situation here!!:(
[AT&T Samsung Galaxy Note I717] darkspr1te:
please pull the latest perl from jcsullins git, delete the two qdload file and run this single model

https://github.com/jcsullins/qdloader

Our initial updates are going to be slow as we learn the bugs, we already are aware of a timing issue and that will affect most users.

I see from the posted logs that it's still expecting data in the second stage, i will look into why it's not closed correctly. please if you could pastbin the full logs , the debug output is very important

Also, can users avoid just reporting same here, we have reports of similar Symptoms but the logs prove otherwise and the solutions are also different.

darkspr1te
[AT&T Samsung Galaxy Note I717] SouL Shadow:
Ok, based on your posted results, everything appears to have worked perfectly! This is great... however, I think the 2nd file being written is wrong. It will need to be built for that specific device. The msm8960 tracks firmware versions when they are installed. Each time you upgrade it records the new version in an efuse. On boot up this value is checked against the firmware being loaded. If firmware is lower then efuse it sets an error and jumps to qdl.

This version check is done in addition to the normal signature check (which can also cause an error and jump to qdl)

I think this reason alone is the main cause of a lot of bricks for the sgs3, htc jewel and evita.

How to fix: recreate the second file based on the firmware that was installed on your device before you bricked.

Darkspr1te: we'll need a script/program to do this on the fly. Eventually we'll be able to read the efuse data to determine the version, but until then the user will need to supply the correct image file(s).

-SLS-

---------- Post added at 01:55 PM ---------- Previous post was at 01:31 PM ----------

Oh, and based on everyone's experience using the hex for msm8960 devices, it appears the 'go' command response is never sent by the device. Not sure why. That's why qpst was always getting hung up on that step.

-SLS-
[AT&T Samsung Galaxy Note I717] Den4ik_2k:
need help

Hi darkspr1te.

Thank you very much for your work. I got to rebuild my E160L. But I have a problem. Sorry for my English, because I write with google translator.

I reflash my e160l. When first boot it was successful. But then he got stuck and rebooted. on the U+LTE splash screen it stuck and does not boot. I reflash again with the pit file from another device (do not know why I did it.)

but Odin give an error and phone to shut down. When connected to a PC qhsusb_dload. I do brixfix of your method and restore my device in Odin mode. But the device is now able to cycle reset, as it was before.

At Mount sdcard in recovery mode gives e:Chan't mount /sdcard/. When cleaning dalvik cache errors. Do not know what to do. I hope you can help me
[AT&T Samsung Galaxy Note I717] klacenas:
Samsung Galaxy Wonder GT-I8150

Hi darkspr1te,

First of all i wanna say thank you for your work here. What a brilliant idea to fix a hard bricked phone.

I'm here because i have a hard bricked phone my self, a new one! It happened after I installed swapper2 from Playstore. It doesn't boot anymore, no recovery,

no download mode, basically no power at all. However it's still being detected as QHSUSB_DLOAD in my computer.

So I'm hoping that this thread might be able to assist me to at least make Odin enumerate and recognize my phone again.

Although I understand the concept of this fix, I'm lacking the knowledge to do this by myself.

I don't know what are files needed? from where and how am I going to extract them?

So I would appreciate any help I can get from you guys.

Here are the details of my phone:

Samsung Galaxy W (Wonder)

Model: GT-I8150

Codename: Ancora

Chipset: 32bit Qualcomm Snapdragon MSM8255T, 1400MHz

And these are the contents of the Ancora.ops

0,partition
1,dbl
2,osbl
3,amss
4,emmcboot
5,adsp
6,boot
7,system
8,cache
9,userdata
10,recovery
11,persist
12,preload

These are the files I have right now:

1. APBOOT_I8150ZSKI3_CL613004_REV00_user_low_ship_EMMC.tar.md5

2. SMD_CSC_GT-I8150-MULTI-CSC-OZSKI3_EMMC.smd.md5

3. SMD_MODEM_I8150ZSKI3_CL613004_REV00_user_low_ship_EMMC.smd.md5

4. SMD_PDA_I8150ZSKI3_CL613004_REV00_user_low_ship_EMMC.smd.md5

I have installed the Qualcom driver from your brixfix and QPST detects my phone as Q/QCP-XXX (Download)

But what do I do next? where can I find these files?

EMMCBLD.HEX

partition0.bin

8660_msimage.mbn

Unfortunately, this is as far as I can get right now, so please HELP me!

Thank you in advance....
[AT&T Samsung Galaxy Note I717] SouL Shadow:
Ok, first of all, since your phone has an msm8255, you'll need the corresponding mprg8255.hex file and an 8255_msimage.mbn. There's a chance that the .hex file is distributed with QPST.

Right now we don't really have a full solution yet. Although one is in the works, there's no time table or any guarantee that it will work for your device.

Don't try anything unless you know what you're doing!

As much as we would love to help everyone unbrick their device, we only have a limited amount of spare time. Currently we're trying to use that time to create the tools needed to properly use the files and methods we've discovered.

-SLS-
[AT&T Samsung Galaxy Note I717] klacenas:
Thank you so much for the quick reply. i did not look inside the qpst folders. will try when i get home tonight. thank you for the explaination.

Update:

I could not find mprg8255.hex in the QPST package. Search the web but no luck. :(
[AT&T Samsung Galaxy Note I717] stevotdo:
I have a msm8660 device. When using hex2bin to create the hex.bin, do I need to specify an offset or just run in without arguments?

The script errors with this:

openMulti send ok

Response: 0e 4f 70 65 6e 20 6d 75 6c 74 69 20 66 61 69 6c 65 64 2c 20 75 6e 6b 6e 6f 77 6e 20 65 72 72 6f 72 0a

Writing 1024 bytes to 0x00000000; 1620548 bytes left.

Invalid response code

I've made my own 8660_msimage.mbn but it shows the same error.
[AT&T Samsung Galaxy Note I717] darkspr1te:
I Checked up on that error, It's Multi Opened failed, Unknown error.

It's possible due to the devies security that it requires a code to be sent before it unlocks the EMMC chip, we are aware of this are will implement that function in due course.

darkspr1te
[AT&T Samsung Galaxy Note I717] SouL Shadow:
It could be because he's trying to write to 0x00000000

My guess is he didn't have the correct partition info.

-SLS-