yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] darkspr1te:
0x00000000 is correct for second stage write to emmc, if it was for the hex then yes that would be incorrect, the hex is written to 0x2a000000

darkspr1te
[AT&T Samsung Galaxy Note I717] SouL Shadow:
Ah, yes. That's what I get for reading/replying 10 minutes after I wake up. Coffee...

Edit:

Isn't command 0x0e Log Packet?

The log packet may be transmitted at any time after Hello by the phone without being requested.

-SLS-
[AT&T Samsung Galaxy Note I717] stevotdo:
Thank you for your quick reply. Is the security code something that I need to find or can that be pulled from the phone.
[AT&T Samsung Galaxy Note I717] darkspr1te:
Yes its a log packet. Log packets can be copied and pasted in to http://WWW.dolcevie.com/us/converter.HTML , its a handy hex to ASCII converter, please put : between spaces.
[AT&T Samsung Galaxy Note I717] darkspr1te:
As it stands the security code is device specific, in open devices it's 000000, revskills has a list and there are other list's but I don't have a URL right now, I will try and find that info later
[AT&T Samsung Galaxy Note I717] darkspr1te:
Double post, please delete
[AT&T Samsung Galaxy Note I717] gregsarg:
Dark..

I've been watching this thread with great interest for some time. and while the korean versions of the note see very little attention in our section, I applaud your work on behalf of this device.

That being said, I've added this thread and topic into the super thread, as a reference for Korean note users, should they stop in to see us.

As you continue to post additions here, the super thread will mirror those changes for all to see.

Many thanks, for your tireless effort in helping other members of this great device....g
[AT&T Samsung Galaxy Note I717] darkspr1te:
Many Thanks for getting the info out there, Updates will be comming soon, i've been involved in a few projects of late that have created new tools, info and solutions, new start to the year and work have delayed but not stopped the development.

darkspr1te
[AT&T Samsung Galaxy Note I717] darkspr1te:
I Have now revamped my debricking tools, many new changes, major changes to the base code as well as the addition of new tools.

goto

Brick Fix V2
[AT&T Samsung Galaxy Note I717] Metzdroid:
Tablet Mode in rooted e160L as per HighOnAndroid

Hi Dark,

Good day! I would just like to ask for assistance as I think I might have bricked my e160L by trying to do this installation from this video: www*dot*youtube*dot*com/watch?v=Yx0a-C4xGTM

The result after doing the final step of the installation (after second reboot), my phone seems to constantly reboot on its own. Please help me. I have never tried doing the 9000lang rom coz I was so afraid of bricking my phone and now I think I did. It really sucks.

Hope you can help me. Thank you.
[AT&T Samsung Galaxy Note I717] darkspr1te:
Boot too recovery guide:- while power is off insert battery, then hold vol up+vol down and press power, when you feel the vibe, release power, when you see gfx release all buttons, then install a cwm recovery via odin- see Dev/rom thread,reboot to cwm/twrp and do cache+dalvic reset, if that fails follow with factory reset from cwm/twrp.
[AT&T Samsung Galaxy Note I717] Metzdroid:
Thanks for the quick response. I flashed tegrak rec.tar file and samsungE160recovery file then did the cache+dalvic reset as well as a cache partition wipe and factory reset. But now my phone is stuck on the U+ LTE boot image. :( I was on the step of putting the 9000lang.zip, Superuser-signed.zip, cwm-160|-update.zip but my PC does not recognize the phone anymore.

Edit: I was able to flash cwm.tar via Odin to my phone, but when I hold vol up+vol down and power, release the buttons after Samsung and vibration, gFx this time did not show. And again I am stuck on the U+ LTE boot image.

By the way how do I put all zip files to my internal sd card? Thanks so much for being patient with me.
[AT&T Samsung Galaxy Note I717] darkspr1te:
Re: No JTAG [SOLVED][JTAG,BRICK]SHV-E160L Korean model

If you do vol down/home and power on at the same time you should get Korean text, at the Korean text press volume up, this gives you download mode. In download mode flash a clean ROM .tar file, watch the flash and as it get to the end and reboots hold down home and vol down to reboot into odin /download mode and flash a cwm from a tar file. Again on the rebooting hold vol up and down, you should now be in cwm mode on a clean ROM, reset cache and factory reset and you will be good, I've done this myself a thousand times during my research and this fixes it every time

sent from the Darkspr1te's lair
[AT&T Samsung Galaxy Note I717] Metzdroid:
Still stuck in boot loop

Thanks again. So here's what I did and downloaded from different threads here.

1. Downloaded HOME_E160L.UH24.1821_CL966093_REV02_user_low_ship_rooted.tar from this thread: [SHV-E160][Root][Stock]How to Root Korean Note via Flashing with Rooted Stock FW

2. Downloaded cwm with this filename: samsungE160recovery.tar from this thread "How to root a korean galaxy note E160L (LGU+) model (ICS) + cwm install"

3. Downloaded Odin wit this filename: Odin3 v1.85 from this thread: [SHV-E160][Root][Kernel]How to Root Korean Note via Tegrak Kernel Setup.

4. Followed your instructions:

- power off phone

- connect usb cable to phone and PC

- run Odin as administrator

- go into download mode: vol down+home+power

- device was identified by Odin (only Auto reboot and F .Reset Time was checked and PDA,

- clicked PDA and chose HOME_E160L.UH24.1821_CL966093_REV02_user_low_ship_rooted.tar file

- watched and finished flashing

- pressed vol down+home after vibration on reboot

- now again on download mode, same settings as before, clicked PDA and chose sam86sungE160recovery.tar

- upon reboot, pressed vol up+vol down and went into recovery mode under the name E110S CWM Recovery Quens Mod

- chose advanced, chose wipe davlik cache --> yes - wipe davlik cache, ***go back***, wipe cache partition (yes), wipe data/factory reset (yes)

- chose reboot system now and watched and waited for reboot

5. I tried waiting even if phone rebooted for many times while not being able to move past U+ LTE image (phone reboots again).

6. Other files downloaded:

- from thread "How to root a korean galaxy note E160L (LGU+) model (ICS) + cwm install" aside from samsungE160recovery.tar file

- cwm-160l-update.zip

- Superuser-i717-ICS-signed.zip

- Tegrak.rec.tar

- from thread [SHV-E160][Root][Kernel]How to Root Korean Note via Tegrak Kernel Setup

- Tegrak-Kernel-Build-41-for-SHV-E160L-UH24.recovery.tar

- Tegrak-Kernel-Build-41-for-SHV-E160L-UH24.zip

- from thread [ROOT/ROM/DEV] Korean Galaxy Note Development and Support

- cwm.tar (i tried flashing this one in download mode instead of samsungE160recovery.tar but when trying to go to recovery mode (vol up+vol down+power) after releasing buttons after seeing samsung name, it does not proceed to recovery mode. Only the samsungE160recovery.tar was successful. Tegrak was also successful but both failed to reboot properly after. I am still stuck in boot lopp issue.

Previous Phone set up:

Model number: SHV-E160L

Android Version: 4.0.4

Baseband version: E160L.FH02.1442.LT

Kernel Version: 3.0.8-966093

se.infra@SEP-68 #1

SMP PREEMPT Fri Aug 24 18:36:50 KST 2012

Build Number: IMM76D.UH24

I know I am asking a lot, but kindly please check my process and files and I would greatly appreciate any form of advice.

Thank you very much and hope your having a great weekend.
[AT&T Samsung Galaxy Note I717] Metzdroid:
Hi darkspr1te, sorry for bothering you. I am just desperate to bring back my E160L to normal and probably/finally flash the 9000lang. I checked your signature links, and I am now trying to get the SHV-E160L.UH24 zip files. But I am having trouble with a lot of its parts, they dont seem to fully download. My connectivity is okay, as for the first 17 files, I was able to fully download 5 of them, most were just partial downloads and stopped. Can you provide me with another link to get the files as I will retry flashing a clean ROM like you advised. thank you.
[AT&T Samsung Galaxy Note I717] SouL Shadow:
Re: No JTAG [SOLVED][JTAG,BRICK]SHV-E160L Korean model

First, I don't know anything about this phone or any samsung phones, however when you describe it as being stuck in a boot loop the first thing that comes to mind is an incompatible kernel.

-SLS-
[AT&T Samsung Galaxy Note I717] darkspr1te:
Re: No JTAG [SOLVED][JTAG,BRICK]SHV-E160L Korean model

I am asking anyone with a 32gb shv model to please contact me. I need a file to help another user.

sent from the Darkspr1te's lair
[AT&T Samsung Galaxy Note I717] prahasta:
Re: [Aug/21,PAUSE/2012][ROM][SENSE3.6/ICS] HolicsROM V1.3 Official with Holics Kernel

Tell me what file..and where the location
[AT&T Samsung Galaxy Note I717] darkspr1te:
Re: No JTAG [SOLVED][JTAG,BRICK]SHV-E160L Korean model

Download my http://www.sendspace.com/file/1s0g60 debrick programs.

Install the windows python (can be uninstalled after)

Run command prompt and CD to directory where you unzipped the file with

CD \folderwherebrixfixis

Then type backup.bat

It will create a folder called backup, zip this up and post to send space the just post the link here.

Darkspr1te

sent from the Darkspr1te's lair
[AT&T Samsung Galaxy Note I717] prahasta:
always failed to download it. can u upload it to mediafire?
[AT&T Samsung Galaxy Note I717] arie001:
SGH-I727 Skyrocket unbricking possibility?

I will be trying this soon on my bricked SGH-I727 Skyrocket. It's stuck in QHS_Download after a CWM flash add is recognized in QPST.

Edit: perhaps I wont be trying anytime too soon since no SHV devices aren't yet supported however the SGH-I727 is awfully close to the SHV-E110S, only difference is the centered home button at the bottom.
[AT&T Samsung Galaxy Note I717] darkspr1te:
I Have decided that this thread has served it's purpose and will now be closed to future posts. Please direct any 'non' SHV-E160L post's to

Brixfix V2

Please can all Ongoing jobs/works migrate to the above thread.
[AT&T Samsung Galaxy Note I717] Clark Joseph Kent:
Closed as per OP, See post above...^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Thank You.
[AT&T Samsung Galaxy Note I717] darkspr1te:
More info

Right, I was not having any luck last night with getting a boot, i think it may have something to do with parttion table, anyway i gave at 4am and hit the sack, this morning i decided to go back to my full dump (the first thing i did once if got the device flashed with the qualcom 8660_msimage.mbn with gives you full emmc access and a diagnostic com port)

anyway i kept going over the partiotn0.mbn file supplied by some of the zips/firmware

i kept saying to my self that is already patched , so i decided to hunt for my original ebr,

well i found it

with you qualcomm device in emmc sd-card mode

do

dd if=fulldump of=ebr-test-dump.bin skip=208801 count=100

count may not be as high as 100, but i wanted to grab extra data and then cut it off using my hex editor,

i then wrote it back to the phone using

dd if=ebr-test-dump.bin of=/dev/sdc seek=208801 bs=512

now my mbr i wrote using the partiton0.mbn file with

dd if=partition0.mbn of=/dev/sdc bs=512 count=1

i was greeted with this from fdisk -l /dev/sdc

Disk /dev/sdc: 15.8 GB, 15758000128 bytes
1 heads, 32 sectors/track, 961792 cylinders, total 30777344 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdc1 1 204800 102400 c W95 FAT32 (LBA)
/dev/sdc2 * 204801 205800 500 4d QNX4.x
/dev/sdc3 205801 208800 1500 51 OnTrack DM6 Aux1
/dev/sdc4 208801 208801 0 5 Extended
/dev/sdc5 212992 213991 500 47 Unknown
/dev/sdc6 221184 225279 2048 45 Unknown
/dev/sdc7 229376 234375 2500 4c Unknown
/dev/sdc8 237568 258047 10240 48 Unknown
/dev/sdc9 262144 263143 500 46 Unknown
/dev/sdc10 270336 271335 500 5d Unknown
/dev/sdc11 278528 279527 500 91 Unknown
/dev/sdc12 286720 307199 10240 93 Amoeba
/dev/sdc13 311296 511999 100352 c W95 FAT32 (LBA)
/dev/sdc14 516096 522239 3072 4a Unknown
/dev/sdc15 524288 530431 3072 4b Unknown
/dev/sdc16 532480 538623 3072 58 Unknown
/dev/sdc17 540672 741375 100352 8f Unknown
/dev/sdc18 745472 751615 3072 59 Unknown
/dev/sdc19 753664 759807 3072 5a Unknown
/dev/sdc20 761856 767999 3072 5b Unknown
/dev/sdc21 770048 790527 10240 ab Darwin boot
/dev/sdc22 794624 815103 10240 60 Unknown
/dev/sdc23 819200 839679 10240 94 Amoeba BBT
/dev/sdc24 843776 3911679 1533952 a5 FreeBSD
/dev/sdc25 3915776 8114175 2099200 a6 OpenBSD
/dev/sdc26 8118272 8736767 309248 a8 Darwin UFS
/dev/sdc27 8740864 9005055 132096 a9 NetBSD
/dev/sdc28 9011200 10035199 512000 95 Unknown
/dev/sdc29 10035200 30777343 10371072 90 Unknown

this exactly matches the pit file i recovered, i think i now have the information to build a correct rawpartition0.xml,

we wont need the patch0.xml file anymore as we actually have our mbr and ebr files now,

there is a possibility the first 3 partitions could be wrong but after looking at data @ 208801 in the raw backup i think they are right, the location was correct thats for sure.

now i am going to restore dd copies of the sbl etc,
[AT&T Samsung Galaxy Note I717] darkspr1te:
dumps

here is the ebr i recovered, plus the partiton0.mbn and pit file for the records
[AT&T Samsung Galaxy Note I717] darkspr1te:
more defined partition table information

copy and paste following into a .csv file and load in your spreadsheet program

Device, Boot, Start , End , Blocks, Id , System,Partiton Name ,File to restore from backup,file to restore from firmware
/dev/sdc1,,1,204800,102400,c,W95 FAT32 (LBA),SMD_HDR,smd_header.mbn,
/dev/sdc2 ,*,204801,205800,500, 4d , QNX4.x,SBL1,,sbl1.mbn
/dev/sdc3 ,,205801,208800,1500,51, OnTrack DM6 Aux1,SBL2,,sbl2.mbn
/dev/sdc4 ,,208801,208801,0,5, Extended,EXT,ebr.mbn,
/dev/sdc5 , ,212992,213991,500,47, Unknown,RPM,,rpm.mbn
/dev/sdc6 , ,221184,225279,2048,45, Unknown,SBL3,,sbl3.mbn
/dev/sdc7 , ,229376,234375,2500, 4c, Unknown,ABOOT,,aboot.mbn
/dev/sdc8 , ,237568,258047,10240,48, Unknown,BOOT,,boot.img
/dev/sdc9 , ,262144,263143,500,46, Unknown,TZ,,tz.mbn
/dev/sdc10 , ,270336,271335,500, 5d, Unknown,SSD,,
/dev/sdc11 , ,278528,279527,500,91, Unknown,PIT,,Shv-e160l.pit
/dev/sdc12 , ,286720,307199,10240,93, Amoeba,PARAM,param.lfs,
/dev/sdc13 , ,311296,511999,100352, c, W95 FAT32 (LBA),MODEM,,amms.bin
/dev/sdc14 , ,516096,522239,3072, 4a, Unknown,MSM_ST1,efs.img,
/dev/sdc15 , ,524288,530431,3072, 4b, Unknown,MSM_ST2,,
/dev/sdc16 , ,532480,538623,3072,58, Unknown,MSM_FSG,,
/dev/sdc17 , ,540672,741375,100352, 8f, Unknown,MDM,,mdm.bin
/dev/sdc18 , ,745472,751615,3072,59, Unknown,M9K_EFS1,efsclear1.bin,
/dev/sdc19 , ,753664,759807,3072, 5a, Unknown,M9K_EFS2,efsclear2.bin,
/dev/sdc20 , ,761856,767999,3072, 5b, Unknown,M9K_FSG,,
/dev/sdc21 , ,770048,790527,10240, ab, Darwin boot,DEVENC,enc.img.ext4,
/dev/sdc22 , ,794624,815103,10240,60, Unknown,RECOVERY,,recovery.img
/dev/sdc23 , ,819200,839679,10240,94, Amoeba BBT,FOTA,,
/dev/sdc24 , ,843776,3911679,1533952, a5, FreeBSD,SYSTEM,,system.img.ext4
/dev/sdc25 , ,3915776,8114175,2099200, a6, OpenBSD,USERDATA,userdata.img.ext4,
/dev/sdc26 , ,8118272,8736767,309248, a8, Darwin UFS,CACHE,cache.img.ext4,
/dev/sdc27 , ,8740864,9005055,132096, a9, NetBSD,TOMBSTONES,tomb.img.ext4,
/dev/sdc28 , ,9011200,10035199,512000,95, Unknown,HIDDEN,hidden.img.ext4,
/dev/sdc29 , ,10035200,30777343,10371072,90, Unknown,UMS,ums.rfs,
[AT&T Samsung Galaxy Note I717] darkspr1te:
dump

Please pm as soon as you have your dump or are close to that point.

i need to see a dump of the smd_hdr partition before any further work is carried out.

Regards

darkspr1te
[AT&T Samsung Galaxy Note I717] tyllerdurdent:
update

Hi darkspr1te,

Sorry, I'm so slow but I'm reading everything and understanding all the information that you upload.

Right, I want to be sure some step because the chinese version has other images programming EMMC.

Copy:

* 8660_msimage.mbn //uploader

* patch0.xml

* partition0.bin

* MPRG8660.hex

to bin folder. image 1.

First, I have to upload the MPRG8660.hex image to the phone using software download?

image 2

Second, what are the order of settings to update the emmc memory?

image 3

I'm in the correct path?
[AT&T Samsung Galaxy Note I717] darkspr1te:
Sucess

For those that have been following my attempt to de-brick a Galaxy note without JTAG, well here you go,

Proof it's not only possible, I have done it. There are still bugs in my method but it does work, and it's possible this will work on many qualcomm devices, finally real control over your qualcomm baseband/radio
[AT&T Samsung Galaxy Note I717] tyllerdurdent:
congratulations

Hi, darkspr1te

Man you r my hero. Really good job, I will continue follow your work and trying to reproduce your success.

:good:
[AT&T Samsung Galaxy Note I717] chrisrotolo:
Persistence pays. Very Well Done. I applaud your efforts.

Cheers.
[AT&T Samsung Galaxy Note I717] darkspr1te:
Why Thank Your Young Sire,

Now if i could just ask aother users to just hold on, dont try this just yet!!!!!

I've learned a lot over the past 48hrs, i haver to just document it and process it a little more, my head is kinda full to overload.

But for those of you that want to IGNORE my warnings (brick past here is return to samsung , sorry)

First get 8600_msimage.mbn i mentioned before, and MPRG8660.HEX also, thats all you need to recover the data (Not a UNBRICK yet, we need to recover your data)
put the two files into a folder and rename MPRG8660.HEX to EMMCBLD.HEX

load QPST latest,
load EMMCSWDOWNLOAD
make sure there is NO tick on emmc program,
make sure there is a tick on load bootloaders
QPST should show you a phone in download mode, with a comport
put a tick next to search paths, select the folder that contains your 8660_msimage.mbn and emmcbld.hex

the two text boxes at the top should contain

EMMCBLD.HEX (not MPRG8660.HEX)
8660_msimage.mbn

click download

first it loads the hex file, you device now restarts it's USB system, then it writes the 8660_msimage.mbn to the start of the emmc chip ( ihave not got a dump of partiton 1 so i dont know what data it contains, i have not fixed my baseband so it could be related, also my touch buttons at the front dont work )

once it's finished, unplug device and remove battery,

If it's worked then when you plug your device into a pc (windows or linux) it should show up as a SD-CARD and comport.

now you MUST follow the next step

connect device to linux box

plug in device to linux pc

type dmesg and look for last listed SD? usb device, for example SDB

the next step you must have a place large enough to put the entire file, 16 or 32 gb

dd if=/dev/sdb or=/mnt/largedrive/shv-e160-full-dump.bin bs=512

no go get a drink or coffee, this is a long process

backup that file to another place, you must have two copies, one for workng on, one for in case we make (or my scripts) mistakes,

more to come

darkspr1te
[AT&T Samsung Galaxy Note I717] E:V:A:
Awesome! Very nice work!

I'm working on a tutorial for this, but you just beat me to it!

A couple of comments though.

1) Please edit some of your posts and use the CODE and QUOTE tags, so we can follow more easily what YOU have been doing, versus what others have been doing etc etc.

2) Probable reason for only 1/20 of your eMMC flashes working, is the 90 sec (default) timing limit for enumerating HS-USB. This can be set in many ways...

3) AFAIK, you dont need to rename the HEX file to exactly "EMMCBLD.HEX", it should be enough to put a lowercase "e" in front whatever filename you have. PBL is looking for that in order to activate EhostDL mode.

4) Could you provide a download link with the essentials from the Mione QDN43 zip, so that we don't need to download 124 MB.

Excellent.

PS. QPST latest publicly available is build 378.
[AT&T Samsung Galaxy Note I717] tyllerdurdent:
progress update

I'm creating the backup of the system.

To begin, the work with the scripts.

For the links for mione look here:

bigota.d.miui.com/QDN43/Mioneplus_QDN43_fastboot_Android_4.0_d3d83nmdk2.zip

I will continue follow the instructions of darkspr1te and update my progress.
[AT&T Samsung Galaxy Note I717] tyllerdurdent:
progress update

Now, I have to run the python script?

---------- Post added at 08:09 AM ---------- Previous post was at 08:02 AM ----------

http://depositfiles.com/files/7t7g94niy

Files_step_1.rar file contains:

8660_msimage.mbn

EMMCBLD.hex
[AT&T Samsung Galaxy Note I717] darkspr1te:
Thanks for the info, I will upload the Mione files, anybody recomend a quick uploader website other than rapidshare.

is it possible that the MPRG8660 hex file supports just flashing of certain areas? does anyone have the protocol?

On my samsung i can activate the QDload at anytime, so if i brick with the incorrect boot loader or via any other reason i can power off and when i power on press my special QDload button i've installed into the phone to activate, which also means i am happy to help with dev testing, it's kind of unbrickable.

E:V:A i understand you are doing a lot dev wok, let me know if i can help. I am really enjoying this :p

I would like to produce at the end a one click solution, do you have a link for QPST ?

Is there a recommended file share site people prefer?

I will also go through and edit my post, sorry about my bad format of post's.

One last question is, i want to upload most of what i've found but am unsure of the license behind some of files ( am still new to androids/samsungs) who would be best to advise me on this ( i dont want to upload imei data for example or a qualcomm paid for file)
[AT&T Samsung Galaxy Note I717] E:V:A:
Use Sendspace for big files. (Max 1GB upload per day.)

Not sure what you mean. But I think yes. You can define multiple code regions to be written in the HEX file. I'm just about to complete a tutorial on that! Not sure what you mean with protocol, but I'll cover the HEX format(s) as well...

Great! What did you connect that button to? (AQP8060 signals/pads ?)

You can defenitley be of help. We need help with MSM8960 which is a bit different beast than yours. We need to know:

a) If 8660 HEX can be used as it is with 8960.

b) If the HEX file is signed in anyway, (Secure Boot 3).

You can find QPST 2.7.378 here.

I can't make ethical decisions for you, but most of those files are code that was supplied with the firmware and your phone, so there should be no problem. And if there's problem I'm sure XDA mods will help you sort it out.

Of course you should always censor any IMEI etc data, before making it publicly available.
[AT&T Samsung Galaxy Note I717] tyllerdurdent:
help

hello darkspr1te

I have some questions because I'm not sure avoid something.

when I connect the phone in usb mode the memory appears without format in windows, but it also happens in linux.

This is normal?

because, it is not supossed to be the android file system there?

another error:

- the script throw me and error with partition0.bin

Could you please guide me here?
[AT&T Samsung Galaxy Note I717] darkspr1te:
Sorry for delay in reply as ive just got back 9pm my time from my job site of today.

Yes its not a normal disk format and what ever you do, DO NOT FORMAT THE DRIVE!!!!

Let me grab a shower and i will upload a bit more info as to where you are right now. I will get tech, sorry but you are at the data recovery point,

SO Brb, let me grab coffee, shower and i will reply.

darkspr1te