Hi
I have just bought a second hand i9000 for a very cheap price because it would not boot, I was hoping I could just reflash it to get it working.
I can get into download mode just fine and have flashed several different firmware versions using odin including jpy, jg5, jpc, jpu, jpk and jm8.
Unfortunately the phone still won't boot and stays on the first black and white “GALAXY S” screen, The boot log stops at “Starting kernel at 0x32000000...”.
Code:
1
-----------------------------------------------------------
Samsung Primitive Bootloader (PBL) v3.0
Copyright (C) Samsung Electronics Co., Ltd. 2006-2010
-----------------------------------------------------------
+n1stVPN 2688
+nPgsPerBlk 64
+n1stVPN 3008
+nPgsPerBlk 64
PBL found bootable SBL: Partition(4).
Set cpu clk. from 400MHz to 800MHz.
OM=0x9, device=OnenandMux(Audi)
IROM e-fused - Non Secure Boot Version.
-----------------------------------------------------------
Samsung Secondary Bootloader (SBL) v3.0
Copyright (C) Samsung Electronics Co., Ltd. 2006-2010
Board Name: ARIES REV 03
Build On: Dec 3 2010 00:34:06
-----------------------------------------------------------
Re_partition: magic code(0xffffffff)
[PAM: ] ++FSR_PAM_Init
[PAM: ] OneNAND physical base address : 0xb0000000
[PAM: ] OneNAND virtual base address : 0xb0000000
[PAM: ] OneNAND nMID=0xec : nDID=0x50
[PAM: ] --FSR_PAM_Init
fsr_bml_load_partition: pi->nNumOfPartEntry = 12
partitions loading success
board partition information update.. source: 0x0
.Done.
read 1 units.
==== PARTITION INFORMATION ====
ID : IBL+PBL (0x0)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 0
NO_UNITS : 1
===============================
ID : PIT (0x1)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1
NO_UNITS : 1
===============================
ID : EFS (0x14)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 2
NO_UNITS : 40
===============================
ID : SBL (0x3)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 42
NO_UNITS : 5
===============================
ID : SBL2 (0x4)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 47
NO_UNITS : 5
===============================
ID : PARAM (0x15)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 52
NO_UNITS : 20
===============================
ID : KERNEL (0x6)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 72
NO_UNITS : 30
===============================
ID : RECOVERY (0x7)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 102
NO_UNITS : 30
===============================
ID : FACTORYFS (0x16)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 132
NO_UNITS : 1186
===============================
ID : DBDATAFS (0x17)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1318
NO_UNITS : 496
===============================
ID : CACHE (0x18)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1814
NO_UNITS : 140
===============================
ID : MODEM (0xb)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1954
NO_UNITS : 50
===============================
loke_init: j4fs_open success..
load_lfs_parameters valid magic code and version.
load_debug_level reading debug level from file successfully(0x574f4c44).
init_fuel_gauge: vcell = 4006mV, soc = 83
reading nps status file is successfully!.
nps status=0x504d4f43
PMIC_IRQ1 = 0x20
PMIC_IRQ2 = 0x0
PMIC_IRQ3 = 0x0
PMIC_IRQ4 = 0x0
PMIC_STATUS1 = 0x40
PMIC_STATUS2 = 0x0
get_debug_level current debug level is 0x574f4c44.
aries_process_platform: Debug Level Low
keypad_scan: key value ----------------->= 0x0
CONFIG_ARIES_REV:48 , CONFIG_ARIES_REV03:48
aries_process_platform: final s1 booting mode = 0
DISPLAY_PATH_SEL[MDNIE 0x1]is on
MDNIE setting Init start!!
vsync interrupt is off
video interrupt is off
[fb0] turn on
MDNIE setting Init end!!
Autoboot (0 seconds) in progress, press any key to stop
get_debug_level current debug level is 0x574f4c44.
get_debug_level current debug level is 0x574f4c44.
boot_kernel: Debug Level Low
FOTA Check Bit
Read BML page=, NumPgs=
FOTA Check Bit (0xffffffff)
Load Partion idx = (6)
..............................done
Kernel read success from kernel partition no.6, idx.6.
setting param.serialnr=0x3134a3d8 0x9bda00ec
setting param.board_rev=0x30
setting param.cmdline=bootmode=2 console=ttySAC2,115200 loglevel=4
Starting kernel at 0x32000000...
Any suggestions welcome
Thanks
Matt
Maybe You shoud use "Phone Bootloader Update" option from Odin? Check this. I'm not sure with that, only try to guess. Make sure before flashing!
Thanks for the suggestion I had already tried “Phone Bootloader Update” and “Re-Partition” with a few stock roms with no success.
I managed to get the phone working by flashing “EUGENE373_SamsungS_Froyo_PDA” as suggested in this thread http://forum.xda-developers.com/showthread.php?t=915668, After that it rebooted into recovery and I then flashed JPY via odin and it all works fine .
Thanks
Matt
Related
Hi All,
I used aWizard to read out my Wizard's ExtRom, but do not know how to write it back.
I want to read out the ExtRom in .nba format, I studied the aWizard , I believe since " pdocread.exe 0 0x3900000 ROM\OS.nba " can read out the os, then theoretically " pdocread.exe ??? 0xA00000 ROM\ExtRom.nba " should be able to read out ExtRom in .nba format.
I do not know about programming, can someone be kind enough to point out what the ??? in above should be.
Will the following info has some hints?
Cmd>r2sd all
***** user area size = 0x1E100000 Bytes
R2SDBackup() - Download type = 5
usTotalBlock = 1 sizeof(SDCARD_SIGNATRUE_TABLE)=512
Start address = 0x80000000 , Length = 0x800 (IPL)
Start address = 0x80000800 , Length = 0xC0000 (SPL)
Start address = 0x800C0800 , Length = 0x40000 ( )
Start address = 0x80100800 , Length = 0x280000 (GSM)
Start address = 0x4E3D4C0 , Length = 0x3900000 (OS)
Start address = 0x743D4C0 , Length = 0xA00000 (EXTROM)
Thanks a lot!
Any idea about " pdocread.exe 0 0x3900000 ROM\OS.nba "?
Is 0 the starting offset address & 0x3900000 the size of the os rom part?
I have read the info in wiki.xda-developers.com, but my programming knowledge is too bad for me to understand it!
(just for reference), i posted a detailed explanation on http://www.spv-developers.com/forum/showthread.php?t=2888
willem
Where is the log:
[R&D Test Tools Log File]
01:31:51 : Launching SW update
01:31:51 : Unpacking KDZ
01:31:59 : KDZ file extraced
01:32:10 : Files were extracted.
01:32:10 : LGMobileDL Load.
01:32:10 : Port = 7
01:32:10 : Connecting to phone
01:32:20 : Check Phone mode = 1
01:32:38 : Phone type check.......
01:32:38 : LGMobileDL.DLL Loading....
01:32:38 : _SetAuthMark Ok : wAuthMark(4649)
01:32:38 : _DetachDLL Call
01:32:38 : _DetachDLL Call End
01:32:38 : Param : Path = C:\ProgramData\LGMOBILEAX\Phone\DZ_GT540AT-00-V20b-CIS-XXX-SEP-20-2010.dz
01:32:38 : Param : moduleDir =
01:32:38 : Param : waitTime = 0
01:32:38 : Param : UsbHighSpeed = 1
01:32:38 : Param : PhoneMode = 1
01:32:38 : Param : BinVersion = V20B_00
01:32:38 : Param : AuthMark = 4649
01:32:38 : Call fn_StartUpgrade
01:33:00 : 3GQCT : wParam = 4, lParam = 0
01:33:00 : Step Complete : DLOAD Change
Click to expand...
Click to collapse
After a while a pop-up window appears and say:
Upgrade Error
WParam: 100
LParam: 6
Click to expand...
Click to collapse
Any help is welcome.
Hi,
I can't find fsck.vfat in order to repair a corrupt internal SD card.
How come it's not that popular (if it exists at all)?
Thanks,
Yaron.
I found there is a build in one patched by samsung, if it was not added by custom firmware.
# /system/bin/fsck_msdos -ny /dev/block/vold/179:1
/system/bin/fsck_msdos -ny /dev/block/vold/179:1
patched by [email protected] 2011/01/21
** /dev/block/vold/179:1
Boot sector contents:
bytes per sector:.............512
sectors per cluster:..........64
number of reserved sectors:...32
number of FATs:...............2
number of sectors are in FAT:.3440 (1720 KB)
cluster mask (bit):...........32
FAT entries:..................440320
first cluster offset..........6784
cluster size(bytes):..........32768
number of sectors:............28180416
hidden sectors:...............0
number of clusters:...........440213
oem name:.....................android { 0x61 0x6e 0x64 0x72 0x6f 0x69 0x64 0x20}
volume serial number:.........466b-16f7
volume label:.................NO NAME { 0x4f 0x20 0x4e 0x41 0x4d 0x45 0x20 0x20 0x20 0x20 0x46}
file system string id:........FAT32 { 0x41 0x54 0x33 0x32 0x20 0x20 0x20 0xfa}
** Phase 1 - Read and Compare FATs
Attempting to allocate 1720 KB for FAT
Attempting to allocate 1720 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
FSNext block (3) is correct, NumClusters (440213)
11950 files, 4180320 free (130635 clusters)
I'm trying to brick my phone. Can anyone suggest a 2.2 bootloader SBL or PBL? I've got 2.3 bootloaders on my device. I just need a bad bootloader to flash.
I can't download from hotfile because I just downloaded something and I'm waiting for 45 minutes. I also have to download a new 2.3 firmware build next.
Can someone just upload 2.2 bootloader SBL to Mediafire for me?
Could you just pull the battery while flashing with odin or cwm
Sent from my MB860 using XDA Premium App
dgowe15 said:
Could you just pull the battery while flashing with odin or cwm
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I need a hard brick, not a soft brick.... It needs to be destroyed. I need a bootloader mismatch... Something that requires JTAG....
Please upload a 2.2 /2.1 bootloader?
there you go hard brick awaits
so so so weird to say that lol
Just flash the 3 button fix while you still have the GB bootloaders. Hard brick mismatch...
I'm next lol...
Sent from my SGH-I897 using XDA Premium App
AdamOutler said:
I need a hard brick, not a soft brick.... It needs to be destroyed. I need a bootloader mismatch... Something that requires JTAG....
Please upload a 2.2 /2.1 bootloader?
Click to expand...
Click to collapse
Preheat oven to 600°. Stick it in a cup of water and put it in the microwave for about 5 minutes, then dry it in the oven for 30 minutes. Would that brick it hard enough for you?
studacris said:
there you go hard brick awaits
so so so weird to say that lol
Click to expand...
Click to collapse
Didn't work.... Got a PBL?
I mean... it won't boot, but it's not a black screen brick.. I wanted it to be DEAD.
Alright.. I got it... I just went into the UART SBL> prompt and did it manually
Code:
SBL> erasepart 0x3
.....
bbm erase part success
SBL> showpart
board partition information update.. source: 0x0
Now Read Images - ID : 1
.Done.
read 1 units.
==== PARTITION INFORMATION ====
ID : IBL+PBL (0x0)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 0
NO_UNITS : 1
===============================
ID : PIT (0x1)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1
NO_UNITS : 1
===============================
ID : EFS (0x14)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 2
NO_UNITS : 40
===============================
ID : SBL (0x3)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 42
NO_UNITS : 5
===============================
ID : SBL2 (0x4)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 47
NO_UNITS : 5
===============================
ID : PARAM (0x15)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 52
NO_UNITS : 20
===============================
ID : KERNEL (0x6)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 72
NO_UNITS : 30
===============================
ID : RECOVERY (0x7)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 102
NO_UNITS : 30
===============================
ID : FACTORYFS (0x16)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 132
NO_UNITS : 1146
===============================
ID : DBDATAFS (0x17)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1278
NO_UNITS : 536
===============================
ID : CACHE (0x18)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1814
NO_UNITS : 140
===============================
ID : MODEM (0xb)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1954
NO_UNITS : 50
===============================
SBL> erasepart 0x0
.
bbm erase part success
SBL> savepart
SBL> reset
Rebooting...
SB
Secure Fail Error
����������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������
Uart negotiation Error
Insert an OTG cable into the connector!
Enumeration TimeOut Error
OND Check Sum Error
����������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������
Uart negotiation Error
Insert an OTG cable into the connector!
Enumeration TimeOut Error
OND Check Sum Error
Just erasepart 0x3(SBL) and 0x0(IBL+PBL) then savepart.
That'll do it
Sent from my SGH-I897 using XDA Premium App
Testing was sucessful... my phone is unbrickable.
congrats buddy . Can you suggest me which/type of soldering machine should I practice with to have some soldering skills before I get a Riff box ??
Thanks.
umanko said:
congrats buddy . Can you suggest me which/type of soldering machine should I practice with to have some soldering skills before I get a Riff box ??
Thanks.
Click to expand...
Click to collapse
Don't use riff. Use UnBrickable mod.
Windows Phone Flashing Started
AMSS File Found:
RM823_12w30_1_prod_generic_amss.esco
ADSP File Found:
RM823_12w30_1_prod_generic_adsp.esco
WPOS File Found:
RM823_12301_prod_238_02_boot.esco
MDM AMSS File Found:
RM823_12w30_1_prod_generic_mdm_amss.esco
MDM DSP1 File Found:
RM823_12w30_1_prod_generic_mdm_dsp1.esco
MDM DSP2 File Found:
RM823_12w30_1_prod_generic_mdm_dsp2.esco
USER AREA ERASE File Found:
RM823_12w30_1_prod_generic_user_area_erase.esco
WARNING: OSBL File is not Loaded
================================================== ====
Windows Phone Lumia Flasher
================================================== ====
If the Phone is ALIVE
1. Power On the Phone and Connect it to the USB Port
If the Phone is DEAD
1. Press and Hold the VOLUME UP button
2. Connect it to the USB Port while still Pressing
the VOLUME UP button
3. Continue to Press the VOLUME UP button for 8 more
seconds
================================================== ====
Sending AMSS Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 449 Bytes
Status : WRITE AMSS CERTIFICATE SUCCESS
Sending AMSS Data Blocks
(Please Wait for 25 Seconds...)
Status : AMSS WRITE SUCCESS
Sending ADSP Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 449 Bytes
Status : WRITE ADSP CERTIFICATE SUCCESS
Sending ADSP Data Blocks
(Please Wait for 25 Seconds...)
Status : ADSP WRITE SUCCESS
Sending MDM AMSS Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 447 Bytes
Status : WRITE MDM AMSS CERTIFICATE SUCCESS
Sending MDM AMSS Data Blocks
(Please Wait for 25 Seconds...)
Status : MDM AMSS WRITE SUCCESS
Sending MDM DSP1 Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 447 Bytes
Status : WRITE MDM DSP1 CERTIFICATE SUCCESS
Sending MDM DSP1 Data Blocks
(Please Wait for 25 Seconds...)
Status : MDM DSP1 WRITE SUCCESS
Sending MDM DSP2 Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 447 Bytes
Status : WRITE MDM DSP2 CERTIFICATE SUCCESS
Sending MDM DSP2 Data Blocks
(Please Wait for 100 Seconds...)
Status : MDM DSP2 WRITE SUCCESS
Sending WPOS Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 1652 Bytes
Status : WRITE WPOS CERTIFICATE SUCCESS
Sending WPOS Data Blocks
[BLOCK 1 0x00000000~0x00FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : C8D9F6A1AF69045EC0339C2EFFC2527D
---------- : D1CAECCFCFC39F1F44C67A5AD3F6C050
Status : WPOS WRITE SUCCESS
[BLOCK 2 0x01000000~0x016573FF]
Data Size: 0x00657400 Bytes
SHA-256 : 98D712C48E828E9816D3F7E84CFDE5DB
---------- : 2C32011C24D4615234D0F613F4EF7B52
Status : WPOS WRITE SUCCESS
[BLOCK 3 0x01697400~0x01FFFFFF]
Data Size: 0x00968C00 Bytes
SHA-256 : 80EB94E3FB5AE03E9091361275A3138E
---------- : 2D0370E5C2A497C74BEA6BEAA43A9E21
Status : WPOS WRITE SUCCESS
[BLOCK 4 0x02000000~0x02FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 07BE87B2AF4D1386F4C6CA136F3E5A57
---------- : 71DC6DDB330A07AAB4493C8AA329BB58
Status : WPOS WRITE SUCCESS
[BLOCK 5 0x03000000~0x03FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 2A3DE5C7CB693B00E257A4E7FB03E834
---------- : 11FAA597F94B220E69E25BD4653BE9B5
Status : WPOS WRITE SUCCESS
[BLOCK 6 0x04000000~0x04FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 16A3B764DD2CCBE5D144B504A919A847
---------- : 2F5DDCBBE2506ACEF6A39800E4DC5124
Status : WPOS WRITE SUCCESS
[BLOCK 7 0x05000000~0x05FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 4A508131A19FC499F19529C55D5D69B8
---------- : D85FA016F8CADE240FA88FA175159699
Status : WPOS WRITE SUCCESS
[BLOCK 8 0x06000000~0x06FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 9E494B017FB7E00D9245C8AEF0F01467
---------- : F3A10341E7441CBEBDE04399AFDD8C5E
Status : WPOS WRITE SUCCESS
[BLOCK 9 0x07000000~0x07FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 2AA1C1C01BA5F8825796F134753C7651
---------- : ABAC4C024CF30CE60B624C4E6C8CD665
Status : WPOS WRITE SUCCESS
[BLOCK 10 0x08000000~0x08FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 6F6EA7A66C4AE1A05CF643378A07E1A8
---------- : 523B29D66201C2FBD4053B19E785DE14
Status : WPOS WRITE SUCCESS
[BLOCK 11 0x09000000~0x09FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 017C4DB9A69575E684BADB7515DBBF59
---------- : 67A6F0DA20F034470D6148B12A1013F4
Status : WPOS WRITE SUCCESS
[BLOCK 12 0x0A000000~0x0AFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 1EFE884A458C910A768D6A60FF74BA8B
---------- : 58F546EB92737ACD1A59169E583CD407
Status : WPOS WRITE SUCCESS
[BLOCK 13 0x0B000000~0x0BFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 713CF0944BA46C6820DCEB7A210C365A
---------- : 7F8A1B0C3E168DE07B46E14907F511FC
Status : WPOS WRITE SUCCESS
[BLOCK 14 0x0C000000~0x0CFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 425A9ED14D4A78F21CDD261AB87F2CF1
---------- : 37080DD8E63F6A9BBBC4E9181AF7B9D2
Status : WPOS WRITE SUCCESS
[BLOCK 15 0x0D000000~0x0DFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 0C09DA5584E22D2709C548F2E5CD05F5
---------- : CFB62CE93C7DAF202A4B92299072B4FB
Status : WPOS WRITE SUCCESS
[BLOCK 16 0x0E000000~0x0EFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : CC14545EF5F62DA50EFADEC5E077FA15
---------- : FE6723E61D703468E0F2B88A3A77008E
Status : WPOS WRITE SUCCESS
[BLOCK 17 0x0F000000~0x0FFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 75D352196D46AC4FED27B84844D89D27
---------- : A8E6C4BD07D46537FA1D66BC533BF017
Status : WPOS WRITE SUCCESS
[BLOCK 18 0x10000000~0x10FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : D6847541FEB0C828C7BE18F045FD2602
---------- : D31D627E75BAA24AD9EBE13E111DCD96
Status : WPOS WRITE SUCCESS
[BLOCK 19 0x11000000~0x11FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 3512321DD2C8349BF40BF6ACD45B82A8
---------- : 970E7902252853F1C75FD6DA3B07416C
Status : WPOS WRITE SUCCESS
[BLOCK 20 0x12000000~0x12FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 970B38B361801866AEB1F9D0E2A6E5FB
---------- : 28066FD1BCF0EF794B57E56439B29152
Status : WPOS WRITE SUCCESS
[BLOCK 21 0x13000000~0x13FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : C8E0BAEDBCFC0A13A125FF17A9DDDA0E
---------- : 91AC3DD74B6E738F3AD53D269F12CFFD
Status : WPOS WRITE SUCCESS
[BLOCK 22 0x14000000~0x14FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : D786A1406E5AF5D0B5354003197BCE87
---------- : F34053A66DF8375001E2DB59D528B21D
Status : WPOS WRITE SUCCESS
[BLOCK 23 0x15000000~0x15FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 47A2B984B6D9C39AF4131C9ED8DB949A
---------- : 82CBC84E0019ECB0E1BABB61E0F47790
Status : WPOS WRITE SUCCESS
[BLOCK 24 0x16000000~0x16FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : D4CEA61B44087F662387735C6AF3F626
---------- : D0A782BCFC893D7CD19A1895A2503AE8
Status : WPOS WRITE SUCCESS
[BLOCK 25 0x17000000~0x17FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 93D0DB4DA824CE4660B96A99A1F65989
---------- : CA45F500E83FC9A53D1D8330B150A80E
Status : WPOS WRITE SUCCESS
[BLOCK 26 0x18000000~0x184A17FF]
Data Size: 0x004A1800 Bytes
SHA-256 : 0CE0CCDE41E4E40B170207CABCE6AA18
---------- : 8FD44C00E21833E6B5926A1F0CDFA40A
Status : WPOS WRITE SUCCESS
Sending USER AREA ERASE Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 396 Bytes
Status : WRITE ERASE CERTIFICATE SUCCESS
Erasing USER AREA
Status : ERASE SUCCESS
Flashing Done!
Total Flashing Time (Erase + Flashing) : 00:06:17
plz i have one the same problem.
it was work good only whatsapp app was not working
after i flashed it hang on nokia logo
otchere said:
Windows Phone Flashing Started
AMSS File Found:
RM823_12w30_1_prod_generic_amss.esco
ADSP File Found:
RM823_12w30_1_prod_generic_adsp.esco
WPOS File Found:
RM823_12301_prod_238_02_boot.esco
MDM AMSS File Found:
RM823_12w30_1_prod_generic_mdm_amss.esco
MDM DSP1 File Found:
RM823_12w30_1_prod_generic_mdm_dsp1.esco
MDM DSP2 File Found:
RM823_12w30_1_prod_generic_mdm_dsp2.esco
USER AREA ERASE File Found:
RM823_12w30_1_prod_generic_user_area_erase.esco
WARNING: OSBL File is not Loaded
================================================== ====
Windows Phone Lumia Flasher
================================================== ====
If the Phone is ALIVE
1. Power On the Phone and Connect it to the USB Port
If the Phone is DEAD
1. Press and Hold the VOLUME UP button
2. Connect it to the USB Port while still Pressing
the VOLUME UP button
3. Continue to Press the VOLUME UP button for 8 more
seconds
Sending USER AREA ERASE Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 396 Bytes
Status : WRITE ERASE CERTIFICATE SUCCESS
Erasing USER AREA
Status : ERASE SUCCESS
Flashing Done!
Total Flashing Time (Erase + Flashing) : 00:06:17
plz i have one the same problem.
it was work good only whatsapp app was not working
after i flashed it hang on nokia logo
Click to expand...
Click to collapse
Well, RM823 is a Lumia 900. What was your purpose for flashing your phone? To debrand it? Usually the rom thats on it is just fine.
thals1992 said:
Well, RM823 is a Lumia 900. What was your purpose for flashing your phone? To debrand it? Usually the rom thats on it is just fine.
Click to expand...
Click to collapse
plz i want to know if the the boot is destroyed or what because the phone powered on.....but hang on nokia logo
otchere said:
plz i want to know if the the boot is destroyed or what because the phone powered on.....but hang on nokia logo
Click to expand...
Click to collapse
Did you first try the hard reset method with the VolDown + Power first? The only other method I'd recommend is using the Nokia Care Suite instead of what you are using. Its much simpler. Just remember to download the latest edition with the CareSuite External cfg file.
One other thing: what phone are you flashing this *onto*? If you tried flashing a Lumia 900 ROM onto a Lumia 920, for example, there is no possible way it will work (although the flashing tool should detect the discrepancy).
By the way, to get to appropriate forums for the Lumia 900, you should go to the WP7 forums (not WP8, such as this) or possibly to a device-specific forum
Oh, and title your thread properly! Seriously, people... if somebody posts a thread with a title like "plz help me" my default response is "No. Go read the forum rules and come back when you can make posts distinguishable from spam."