View Full Version : Nokia 808 flashing problem
Hey guys!
My 808 emmc memory got full and couldn't manage to delete anything since the phone was running insanely slow. I connected the phone to PC, failed to read it and emmc got locked up, phone doesn't see it anymore. I am trying to flash it completely with emmc, but I get the following error in Phoenix. Please HELP!!!
Update server loaded
Asic CMT: Start programming 2448863 KB...
Asic CMT: Programming data sent: 0%
Asic CMT: Programming data sent: 10%
FUR: ALGO reported error in Control Frame. Unable to continue.
ERROR: Programming error reported for asic CMT
-- Error Type 0x05
-- Error Specifier 0x0F
-- Offending Addr 0x01D9C000
-- Expected content 0x00000000
-- Detected content 0x00000000
Error sending Message Block Command 0x64 - 0x8401F11F
Error when flashing Algo (0x8401F11F)
Unable to flash phone 0x8401F11F
So, it gives me an error when I flash the phone with emmc file selected. Withoud emmc, phone flashed successfully. How to flash emmc?
OK, so I don't get it now. Phone flashed the firmware successfully according to Phoenix, but is stuck in a reboot loop. It used to boot up, but insanely slow since it didn't see emmc. How to flash emmc in Phoenix?
Flashing started
Creating product data items list
Product data items list created
Backup not required
Flashing phone
Initializing
Scanning image files...
Waiting for USB device...
Loading secondary boot code: 15168 bytes
Secondary boot loaded
BB Asic Index is: 00
Asic ID is: 000000030000022600010007400C192103032108
BB Asic Index is: 00
EM Asic ID is: 00000C35
BB Asic Index is: 00
EM Asic ID is: 00000C30
BB Asic Index is: 00
Public ID is: AE5C0000FFFB7C40A522DB2BADD05A632659F55B
BB Asic Index is: 00
Asic Mode ID: 00
BB Asic Index is: 00
Hash: 3AB5DB70B45D23F1ADEEBB5734160706
BB Asic Index is: 00
ROM ID: 2CAC45E23BC33C8B
BB Asic Index is: 00
Device type is: 05
Device Index is: 00
Manufacturer code: 0000
Device ID: 0000
Extended device ID: 0000
Revision ID: 0000
BB Asic Index is: 00
Device type is: 04
Device Index is: 00
Manufacturer code: FFFF
Device ID: 0000
Extended device ID: 0000
Revision ID: 0000
BB Asic Index is: 00
Device type is: 00
Device Index is: 00
Manufacturer code: 0000
Device ID: 0000
Extended device ID: 0000
Revision ID: 0000
BB Asic Index is: 00
Device type is: 00
Device Index is: 01
Manufacturer code: 0000
Device ID: 0001
Extended device ID: 0000
Revision ID: 0000
BB Asic Index is: 00
Device type is: 03
Device Index is: 00
Manufacturer code: 00EC
Device ID: 0060
Extended device ID: 0000
Revision ID: 0032
Loading update server code: 869856 bytes
Update server loaded
Asic CMT: Start programming 248616 KB...
Asic CMT: Programming data sent: 0%
Asic CMT: Programming data sent: 10%
Asic CMT: Programming data sent: 20%
Asic CMT: Programming data sent: 30%
Asic CMT: Programming data sent: 40%
Asic CMT: Programming data sent: 50%
Asic CMT: Programming data sent: 60%
Asic CMT: Programming data sent: 70%
Asic CMT: Programming data sent: 80%
Asic CMT: Programming data sent: 90%
Asic CMT: Programming data sent: 100%
Programming complete
Asic CMT: Verifying communication to device...
Mobile device flashing completed.
Waiting for phone to boot up
Bootup successful
Verifying communication to product (before flash finalizing)
Communication verified
Product code changed
Doing factorysets
Factorysets complete
Loading default data to phone
Loading default data to phone
Getting Data Package
Reading product state
Starting backup/restore sub-procedure: data item pre-delay
data item pre-delay
data item pre-delay
Sub-procedure completed: Succeeded., result code: 0
Starting to backup/restore data item: ProductProfile, version: 1.1
Data Item backup/restore completed: Succeeded., result code: 0
Starting backup/restore sub-procedure: data item post-delay
data item post-delay
data item post-delay
Sub-procedure completed: Succeeded., result code: 0
Backup/restore result: 0 out of 1 items were not backed up
Default data loading complete
Stopping all operations, returning phone to default mode
All operations completed
Firmware updating succeeded.
myname24
2015-06-30, 20:05
i also have the same problem . 16GB drive shows nothing and phone insanely slow . Also like you i can only flash rootfs without emmc . I'll be glad if someone gives us a solution
i also have the same problem . 16GB drive shows nothing and phone insanely slow . Also like you i can only flash rootfs without emmc . I'll be glad if someone gives us a solution
How did yours mess up? My memory got full while recording, had like 5MB left and the phone got so slow that I couldn't delete anything. I connected it to PC which failed to read the memory for quite a while. I disconnected the phone, and mass memory all of a sudden disappeared.
myname24
2015-07-01, 09:45
Really i don't know . But i don't think it got full or low storage . Still same effect
aspergerguy
2015-07-01, 13:56
Very common for mass memory to fail upon 808 and sometimes only way of speeding it up fractionally is to flash Delight CFW to free up phone memory, but usually still can't use camera unfortunately even if memory card in place.
Very common for mass memory to fail upon 808 and sometimes only way of speeding it up fractionally is to flash Delight CFW to free up phone memory, but usually still can't use camera unfortunately even if memory card in place.
So, I just earned myself a brick?
myname24
2015-07-01, 16:45
I can use the camera using the memory card but the whole phone is slow as hell
Ever tried to format the mass memory using a computer?
And did you try to do a dead flash?
(if you dont know what that is,
http://forum.symbian-developers.net/flashing-tutorials-%28updating-and-downgrading%29/%28tutorial%29-nokia-dead-phone-usb-flashing-with-phoenix-service-software/
should help you)
Very common for mass memory to fail upon 808 and sometimes only way of speeding it up fractionally is to flash Delight CFW to free up phone memory, but usually still can't use camera unfortunately even if memory card in place.
Is it something that is inevitable for all 808's?
Does all the processing write and wear out the emmc even when using an SD card?
Any buying tips, worth $120US?
aspergerguy
2017-05-22, 13:02
Is it something that is inevitable for all 808's? Any buying tips, worth $120US?
Certainly not as still using 808 first acquired daily, have come across issue in two 808's bought for spares only.
Pricing sounds about reasonable considering this current auction in US:http://www.ebay.com/itm/Nokia-808-PureView-16GB-White-Unlocked-Smartphone-/252940660248?hash=item3ae4702e18:g:T4MAAOSwX61ZGmJ n
I bought an 808 in August 2016.
Not long ago, but i shot several thousand pictures with it.
Its still working well. I always use an SD card for storing pictures and I noticed that the phones sometimes gets quite slow overall if I have too many pictures on the SD.
Note that I use it only as a camera and for the very occasional symbian game.
Any site to order 808 emmc? Or is any other Nokia emmc compatible with 808? Or just have to find another 808
Any site to order 808 emmc? Or is any other Nokia emmc compatible with 808? Or just have to find another 808
It's generally not something you can replace.
The chips are typically BGA (or even flipchip in the worst case) it is pretty much impossible to remove and resolder.
deutch1976
2017-05-30, 09:33
Will this help somehow?
http://forum.gsmhosting.com/vbb/f609/nokia-808-rm-807-successfully-flash-atf-1892792/
Will this help somehow?
http://forum.gsmhosting.com/vbb/f609/nokia-808-rm-807-successfully-flash-atf-1892792/
Or this :>
https://www.youtube.com/watch?v=OkjOwuSEzKU
It's generally not something you can replace.
The chips are typically BGA (or even flipchip in the worst case) it is pretty much impossible to remove and resolder.
Mobile shops here seem to resolder such chips without problem. Don't know how, but they do it. I guess being a poor country and having lots of broken things, they do wonders :)
Of course it's possible, but not "homework "
Probably a lot safer to look on eBay
http://m.ebay.com/itm/Nokia-808-PureView-16GB-Unlocked-WHITE-IN-MINT-CONDITION-TOP-COLLECTIBLE
vBulletin® v3.8.8, Copyright ©2000-2025, vBulletin Solutions, Inc.