I hope someone can help me. I tried almost everything. My wave just won't boot normally. It all started when I tried to downgrade from Bada 2.0 (S8500XPKH3) to 1.2 (S8500XXJL2) and got a security port error while flashing (used Multiloader 5.65). My wave wouldn't boot up so I got someone to repair it with JTAG. Good thing it was revived. It can now go to download mode, however, i tried flashing almost all firmware versions (Bada 1.0, 1.2, 2.0) in different regions from samfirmware but to no avail.
I browsed through the forums hoping I can get an answer but I didn't see any similar case. I'm sure I'm doing the flashing right 'coz I get "All files complete." when flashing is done. Only that, every firmware that I try, it just stays in the logo screen when it starts up.
I'm looking forward for any response.
Best regards.
I guessed you have done all well. But still try this process:
1. Download a fresh, full and original firmware for your region from samMobile.com
(The firmware version does not matter, but it has to be full and for your region).
2. Make sure your battery is fully charged
3. Remove SIM and memory card from phone.
4. Ensure that all kies drivers are successfully installed.
5. Use multiLoader v5.65
6. Cross-check that your USB plug is not damaged (if possible use another one)
7. When flashing, make sure you tick the FULL DOWNLOAD option in multiLoader.
Try the above and report back. Best of luck.
yeah you should tick boot change and full download for a complete fresh installation
Good thing it was revived
Click to expand...
Click to collapse
Depend on how it was repaired via JTAG...
Maybe NV items are overwritten... this could be bad.
It is not the best idea to use Fullflash from others...
I have RIFF Box experiences...
Best Regards
P.S.:
Try to flash some Rsrc2_S8500(Mid).rc2
Maybe Bluescreen tell you what is missing...
adfree said:
Depend on how it was repaired via JTAG...
Maybe NV items are overwritten... this could be bad.
It is not the best idea to use Fullflash from others...
I have RIFF Box experiences...
Best Regards
P.S.:
Try to flash some Rsrc2_S8500(Mid).rc2
Maybe Bluescreen tell you what is missing...
Click to expand...
Click to collapse
Thanks for the tips guys. I tried the routine checking. I've also tried different a different pc. Same thing.
I'm more inclined to this adfree. NV items might be corrupted. I just know the basics of flashing.I tried several Rsrc2_s8500 (Mid) and yes I got a blue screen with details. I don't know how to interpret it myself but I remember there was IMEI not active. Will post the details later. Hope you or someone can share your thoughts.
Best regards.
I tried S8500XPKH3 again with Rsrc2_S8500(Mid).rc2 and I got this from Multiloader 5.65:
Download Start Ch[0]
BootLoader 1703.9KB OK[0.7s]
Dbl 281.5KB OK[0.8s]
Wait reset !!
Amss 12740.3KB OK[5.0s]
Apps 26214.4KB OK[12.3s]
Rsrc1 37748.7KB OK[14.4s]
Rsrc2 2884.3KB OK[1.3s]
FFS 49217.5KB OK[111.8s]
CSC 36085.8KB OK[106.0s]
SHPAPP 203259.9KB OK[368.3s]
All files complete[638.0s]
Phone reboots and comes up with blue screen:
S/W version: S8500+XP+KH3
Modem: Q6270B-KPRBL-1.5.45t
SHP: VPP R5 2.1.1
Build Host: S1-AGENT08
Build At: 2011/08/16 20:56:16
Aoo Debug Level: 0
ASSERTION_ASSERT: 0 failed. (file SysSecureBoot.c, line 4193) BoAn4193
<Call stack information>
PC = 4000C8D3 OemDumpRegister
LR = 4000C8D7 OemDumpRegister
<Mocha Task Call stack>
_SysAssertReport
__SysSecBootReadNetLockInfoFromFile
ALL HW Information:
HW VERSION: S8500_rev07
IMEI VERSION: Not Active
RF CAL DATE: Not Active
Bad Block Information:
nNumBMPs: 0
nAge: 0
Run Time Bad Block Occurred:
Init BMPs - 2, Current BMPs = 0
Nucleus Task Information:
Running Task name - Mocha Slices = 0000001E Wait = 00000000
Signal = 00000000 Priority = 0
I've been working on this for a week now but no matter what firmware I flash, i can't get my wave to boot normally
Try qualcomm tools to activate imei
ask Adfree or use google to find the qualcomm tools program and then make your imei active using your pc.
what region was your 8500 originally?
remember that different region firmware use different boot files.
Try to use the boot files that was on your wave originally.
For some reason, it's showing "IMEI not active" when I get the blue screen after flashing with Rsrc2_S8500(Mid).rc2.
I read adfree's qualcomm tools guide and it was more on editing the product code. And, i can't access the configuration mode/hidden menu since I can't boot the phone normally.
IMEI is NV item 550 and ...
But it is secured by...
I have never tried on S8500...
Lost IMEI is enough evidence, that NV items are corrupt/missing/damaged...
I'll try to analyze your Error message...
.. will report later.
Best Regards
Edit 1...
SysSecureBoot
SysSecBootReadNetLockInfoFromFile
Click to expand...
Click to collapse
Maybe also Netlock? So maybe without IMEI Security check failes...
I think the guy who tried to resurrect my phone was using JTAG Medusa. Is there any possibility something went wrong during the process? I was just happy that the phone can go on download mode but didn't expect that whichever firmware I try, phone is just stuck on logo.
With regard to the IMEI, should i recover it, will it have a good chance to fix the problem? Can i use qualcomm tools even if the phone can only run on download mode?
if use medusa make this erase full flash after that write full from support stop writ flash in 6% in flash procedure after this flash full flash all files with boot after this pach wit z3x pachv2.Repair imei and al by ok
tested with s8500 whoo come in donload mode with 3 butons vol - lock and power
in first when try flash bada 1.0 soft after ffs write in screen see missing fota 2.0 please instal instal bada 1.2 after this
@OP:
Your SysSec data, which is closely related to NvData, has been damaged, probably by JTAG ovewrite. These data are encrypted by device-unique key.
It is possible to repair it without JTAG, through modified FOTA. But I don't think I'm the one to try this. Last time I played with that data I damaged my BL3. :\
Thanks for those who provided their insights. I kind of gave up last week and had to bring my phone to the service center. Fortunately or not, the tech had to replace the motherboard which cost around 170 USD including the "repair fee". My phone's back with a new motherboard and ready for some risky flashing again. Hehe.
Anyway, thanks again guys. Good day to y'all!
full erase flash only 6% from full after thath full flash with orginal flasher now read wit rj45 cable with z3x nvm from phone in 550 string see if imei is 359321654 need write 8a31391256 and write in phone now imei ok or select in z3x i 5500 put orginal imei and sn repair all come good and working
after all ok read full again from phone search s8500 and see you detail if need edit as your orginal string
ЄЇ~GT-S8500............їµ±№....................................TMU.....2010-06-01....АМАз±Х..................S8500BOJE7_TMOJE7...564C......9750......86210000114318......KAC007021M(S8500)...-
During my plays with RIFF JTAG and few stupid experiments with full erase I'm now facing same problem...
Strange, but this happens with my own JTAG dump...
Will see how long I need to repair this...
Best Regards
It seems no good idea to be. To erase whole NAND via JTAG...
Anyway... long time and luck... I was able to bypass Boot Cycle and then to Restore NV items via QPST...
Maybe 1 part of solution is, to use Firmware BOJE7 with Bootloader XXJEE...
Then maybe your handset start...
Now you can access menu to change to Qualcomm Diag Port for restoring NV items...
Best Regards
Hello Everyone,
I am by no mean a novice in software/hardware repair, however, this Note 3 got me baffled. Not even the Cellphone repair shop was able to flash it, he tried 4.2, 4.3, 4.4 and a PIT file and still couldn't get it. I also tried ODIN 3.07 and 3.09 with a PIT I got from the Heimdall thread with no avail.
I also tried the Heimdall Tutorial and also failed. I have the option to send it to mobiletechvideos but $70 is a bit too much for me right now and they aren't even accepting new orders.
The phone originally freezing so every time it became unresponsive, I would pull the battery out. I have pulled the battery out at least 10 times. Then one time, I pulled it out and put it back in, restarted the phone, then the phone hung at the Samsung Logo.
However I have access to the download mode by pressing PWR + MIDDLE + VOLM DN combo. the following message appears:
ODIN MODE
PRODUCT NAME: SM-N900T
CURRENT BINARY: Samsung Official
SYSTEM STATUS: OFFICIAL
KNOCK KERNEL LOCK: 0X0
KNOCK WARRANTY VOID: 0X0
QUALCOMM SECURE BOOT: ENABLE (CSB)
AP SWREV: S2, T2, R2, A3, P2
WRITE PROTECTION: Enable
UDC START
Downloading...
Do not turn off target !!
Now, one thing worth mentioning, is when i try to factory reset using PWR + MIDDLE + VOLUME UP, I get the following message:
MMC: mmc_read fail
Movinand Checksum Confirmation Fail
by the way I don't have an SD card in there.
When I hook it up to ODIN 3.09 and try to insert the firmware and PIT file, here the message I get on the phone:
SECURE CHECK FAIL: PIT
ODIN: flash read failure
and on ODIN, it says:
Repartition Operation Failed.
I believe the NAND chip is corrupted and I might need to just get a new Logic board. But its worth a try before I try to shell out $50+ for a new one.
If anyone can help me with this, as in HOLD MY HAND and guide me through this by providing links etc, I have $20 in PayPal ready. If you are in the Orange County, California area, I can drive to you to give you your $20 and i'll buy you a Starbucks Frapuccino. Please help!
Call me a quitter, But I've sold my problem to someone else. Not worth putting more money into the thing. Thanks everyone!
I don't blame you, I Prolly would've done the same thing in that case
Mods need to lock this thread js
Pretty much what the title says. My phone blue screens. This is the third time that it's happened in the past week...and I first installed it last week...lol
Got an LG G3 D855
Latest version of Paranoid Android
Did a completely clean install: using TWRP, wiped all available partitions, then flashed PA zip.
The first time it happened was the day I installed. I just kinda shrugged it off and went ahead with making it mine. And it happened earlier today and I went ahead and ignored that too. It just happened a third time (few hours after the second time; exact time after is shown below by uptime).
When it blue screened it gave me the following message on screen (without the astrisks)
*****************************
---------------------------------------------------------------------------------------
Subsystem Crash! : modem (susbsys-restart Resetting the SoC)
---------------------------------------------------------------------------------------
DemiGod Crash Handler : Subsystem Crash ! : modem (subsys-restart: Resetting the SoC)
Press key to choose Dload Mode or Reboot.
1) Volume Up : Dload Mode.
2) Volume Down : Reboot.
If you choose Dload Mode,
Please do following action.
1) Dload Mode. Please connect USB.
2) Get the ram dump image using QPST Configuration
---------------------------------------------------------------------------------------
Board Info
rev.:1.0 speed,pvs: 3,7 serial : muhSerial
---------------------------------------------------------------------------------------
ERR crash log report. Version 3
Error in file wl1trm.c, line 404
Error message: WL1TRM: wl1_trm_grant_callback: Invalid Parameter(%d %d %d)
Time of crash(m-d-y h:m:s): 8-14-2015 21:32:46
Uptime (h:m:s): 5:12:38
Build ID: MPSS.DI.2.0.1.c1.13-0046-M8974AAAAANPZM-1
param: (0x5, 0x0, 0x0)
aux_msg:
qsdm_dbg_msg:
*****************************
Also, from what I've been able to find out, I think that that file might have something to do with radio functions, but I can't be sure because I just did a quick search.
Help would be greatly appreciated!
You should look in your device forum for help on this. I don't think it's a ROM specific issue. I'm pretty sure its a device specific issue
Try to Flash official stock Rom via KDZ or TOT&DLL method.
So i got one of these vs985s. and nothing. screen lit up but nothing else.
so i had a unknown or damaged usb device .long story short
got it in 9008 i follow all the guides emmc and ap test past.
but when i to the sd ram test i get a error of
========DDR TEST START
Test level = 0(check data/address line)
sbl1 partition write FAIL.. senctor 0x28000
WRITE FAIL During ddr test..
Aborted..........
Also everytime i click a restore boot image in any version of board diag tool whatever partition im trying to restore write fails....
Now i remeber back on my g2 i got the 9006 mode i was able to zero all the partitions in linux when it mounted 30 somthin drives.
Is there any info any one could give me as i have followed all the guides.. But might be missing something somewhere.
any help is greatly appreiciated
I have the exact same problem here with my father in law's D852. The phone was never rooted. I was trying to unbrick it but it didn't reboot after flashing sbl1. So I decided to try a stock rom form another source and that's when this happened. Trying to go back to the first rom didn't work, even after erasing the entire emmc. My guess is somehow, we activated permanent paper weight mode. I hope someone more qualified than us can help us, or at least confirm our phones are good for recycling...
I got a hard bricked HTC Desire 816 single SIM, EU version, Qualcomm MSM8928 Snapdragon 400 chipset
I know for sure it's a HTC single SIM phone, the rest I googled with the help of part numbers printed on various parts of the phone.
I can post the numbers if it helps to identify the phone
I guess it's an European model and not an import.
When I connect it to a PC I get a Qualcomm HS-USB QDLoader 9008 (Com4) port detected
I fully charged the battery on an external charger.
I have tried this guide: https://forum.xda-developers.com/t/guide-unbrick-htc-816w-a5_dug-from-hard-bricked-9008.3391110/ but the phone does nothing, when I press Vol- & Power button.
I see the phone in various SW like QFIL but I have no idea what firmware is the correct one.
I would like to read the whole phone content to identify which firmware I need - but how?
Or is there a other how identify the phone? Perhaps restore only the preloader, bootloader ... ?
Any advice how to proceed?
Thank you
Some progress ...
I need QPST or something similar, what is able to flash in emergency download mode - done
I need to download and extract probably suitable firmwares - done
I need a suitable programmer for the MSM8928 - probably done
But the firmwares are not in an usable format for the QPST Software Download.
How do I convert them to mbn or hex?
The firmwares are incomplete, it seems I need a complete mmcblk0 dump ...
It seems I'm out of luck.
I've tried different tools under Windows and Linux (to rule out Windows driver issues) but the result is the same.
I can download the prog_emmc_firehose_8928.mbn but that's it, the port stops responding after that.
I've also tried to boot two images (A5_DUG and A5_DWGL) from a SD Card and nothing, no sign of life.
I know need a A5_UL image but I thought the phone should show at least some sign of life but nothing :-(
The only sign of life is the port in EDL mode, when connected to a PC.
Is the phone dead or is there something else I could try?
I'm out of ideas ...
Some news.
I got some responses to SAHARA commands from the phone:
Attempting to switch device to mode: Command Mode
Device is awaiting client commands
Serial Number: AAA - BBB
Unknown ID 1: 0
Unknown ID 2: 0
MSM HW ID: 32993 - 000080E1
OEM Public Key Hash Hex:
========
Dumping Data For Command: 0x06 - Read Debug Data - 3904 Bytes
========
SBL SW Version: 0
========
Dumping Data For Command: 0x00 - NOP - 16 Bytes
========
Requesting mode switch from Command Mode (0x03) to Memory Debug (0x02)
Devices responded with an error: Invalid Command
Port Closed
Firehose programmer download:
/dev/ttyUSB1 USB VIDID=05c6:9008 Qualcomm CDMA Technologies MSM QHSUSB__BULK
Connected to /dev/ttyUSB1
Reading hello handshake
Device In Mode: Image Transfer Pending
Version: 2
Minimum Version: 1
Max Command Packet Size: 1024
Device requesting 80 bytes of image 0x0D - EHOSTDL
Sending image /prog_emmc_firehose_8928.mbn
Image /prog_emmc_firehose_8928.mbn successfully sent.
If there are no more images requested, you should send the done command.
Sending Done Command
Done Command Successfully Sent
No response from device
It seems that the prog_emmc_firehose_8928.mbn is not the correct one ...