Most of us would not deny , because of the lack of clues to solve a case of damage to the phone , hands armed with hot water ( blower ) so hot inflatable blower itch again there sini.Apa the patient comes in dead condition total , all inherent components , will not qualify hemburan death of solder flux fumes and beceknya scrubs .
I did not deny feeling groggy in the liver occurred when the patient comes in a dying condition , life would not hesitate to die , is not that the human body technicians aka the doctor , the patient came dying , surgery continues to remain dead money , try if the phone technician , killing hp dying might actually overdrawn money .
Oh well do not have to envy the doctor at the clever and too expensive school , we control and develop their own potential , because the more accurately diagnose the damage , the closer the keberhasilan.dan more precise handling , the further as problems although the practice is not as easy as the theory , but at least we 've got a map for walking in the right direction .
We start with a map of troubleshooting boot problems on nokia 6600 , so that proper diagnosis and treatment , as much as possible the actual chronological ask hp to the owner about the cause of the damage , but sometimes the owner does not want to admit about the actual cause of the damage to the hopes not want to get the expensive rates . " hp kecemplung depleted water , ngomongnya not all tau - tau napa2 die alone .... cepek dehhh " .
Because if it causes physical damage caused by incidents such as floods hit the water , slamming his wife for cheating ketauan occupied himself for fun , it is 99.99 % handling damage the hardware , but if the results of the interrogation revealed the damage caused by depleted porn files received from Bluetooth , for playing games using that child , his friends make facebookan dipinjem , or death itself , the most likely is a software problem .
But keep in mind , handling software & hardware treatment interrelated , clicking - allocation damage is happening on power unit or the unit of data handling software needed to use the flasher like JAF or UFS or other damage through handling and detection software would also be worth it when the phone is fully corrosion crust or in the short condition due to excess water flow .
Standard steps that must be taken when handling hp first Matot namely :
* check through the battery connector , short or no hp by using mul titester ( AVO meters ) .
* check the battery capacity or try with another battery .
* check the battery connector .
* Check the function switch on / of mencharging his way .
* Check the condition of boots using flasher media .
* check the LCD socket connection , bad connection can result in death and hp as failed when the flashing process .
ERROR CODE ON UFS
Error 2
UFS - disconnected software , then close , then open again click "connect "
- could be due to the UPP , or also because of problems 13Mgh Clock IC ( long dimension located near UEM )
Error 4
Could be due to problems or voltage UPP UPP who come in ( v2.3 & v2.5 voltagenya 1.8v while voltagenya 1.5 v 3.2 )
Error 6
Problem in ic ram
Once we do cheking standard as above yield condition is not short hp , good battery connector , then we do detection through software with the results :
Error 1st , 2nd error
Total dead
After checking standard as we did above tersbut hp condition does not produce short , conektor good battery , then we do detection through software dngn results :
Error 1st , 2nd error , which means the problem on power
handling
1.ukur with multitester , note the current consumption required when switch on / of pressed .
0mA
-periksa/ganti R132 and R133
- heat the , reprint or replace UEM
0 - 25mA
Although rare clock can also be caused
- heat the , reprint or replace upp then flash again
30mA
Still software problems
emi - check IC and components around the interface flash fleas diboard
- check also RJ45 cable ( cable flash )
50 - 100mA
UPP - switch ( D100 )
- replace flash ic 0/FLO ( D314 )
then re - flashing
150mA
There is still a short on the circuit
UI - check the protective tape , when peeled off causing short bias
Ok 1st , 2nd error ( or other error messages appear )
If the phone comes in condition white screen display , 4x display nokia , nokia only display , contact retailer or fails to boot , and when done check the software functions appear OK message 1st , 2nd OK , it is most likely a software issue
To overcome this did re flashing , do yourself if unsuccessful improvisation , improvisation can be tried as a full erase , china firmware contents , format user area etc. .
But my message , always do and get used to backup PM as a precaution in case of imei question mark .
As learning , for this case we consider the process of flashing the obstacles , the component responsible and the suspect is flash ic ( there are 4 ) and UPP .
Then the steps taken are :
To know the flash ICs which are problematic , then erase flash ic one by one to fill erase address as follows :
FL0 ( D314 ) start 02000000 -end 027FFFFF
FL1 ( D316 ) 04 million start -end 047FFFFF
FL2 ( D315 ) 06 million start -end 067FFFFF
FL3 ( D317 ) start end 007F0000 - 007FFFFF
Ic flash erase failed to address each, meaning the flash ic is damaged and needs to be done penggantian.jadi with this method we can find out where the flash ic or maintenance that needs to be replaced ( or heat the reprint ) , because when the fourth change ic the flash without sorting out which ones are good which are faulty , we make the problem away .
Now, what is done after reimbursement ic flash ?
FL0 ( D314 )
Flashing back and fill imei using RPL file suit in UEM IMEI
FL1 ( D316 )
Flashing back and do the formatting features user area
FL2 ( D315 )
Flashing back , fill IMEI using IMEI RPL file suit diUEM , do init simlock and fill with good PM file .
FL3 ( D317 )
flashing back
Die within 35 seconds after booting
Try replacing N380 , if not managed phone system means the result is still diawasi.hal " watchdog " system is tasked with thwarting the boot when the data IMEI 1 ( location at UEM ) and IMEI data 2 ( location in flash ic D315 ) is not the same / sinkron.data missing or corrupt IMEI is located on FL0 ( D314 ) and not on FL2 ( D315 ) .
But if we do that we buy RPL charging using a credit
This in FL0 ( D314 ) without erase the FL2 ( D315 ) , then 35 seconds mati.Pointnya , did erase the FL2 ( D315 ) first, or full erase also does nothing , then just fill / write RPL file .
Case 35 seconds of death can also result UEM ic is damaged and needs to be replaced , to determine whether the UEM ic is damaged or can still be used , this time UFS3 can not do it , who can do JAF , MT Box , universal box , MX key capable of doing UEM read it with features .
After clicking on the read UEM UEM IMEI read if there is a mixture of the alphabet ( eg 3550D10003B197 - X ) can certainly have damaged the UEM , UEM bought new in stores spare parts are to be believed ( the gini weve hard seh ) , plug it in and fill it with any RPL ( default is on file flasher box )
SIMCARD REJECTED
As a result of active or simlock IMEI data corrupt to display a question mark ( ? ? ? ? ? ? ? ? ? ? ) This condition is also still around issues its IMEI with RPL file , try doing double click init simlock and info if the results appear IMEI locked and a sign asked berdetail data ... FFFF ... then do write RPL process as the above step , then use the features init simlock and write PM .
CONTACT RETAILER
Conditions appear "contact retailer " because LFFS corrupted or not formatted , self test function on the phone system fails to do its job , then the actions that are performed :
1 . do format user area features
2 . it could be a trick 4 fingers , for those who bother to train your fingers to press the call button , * , 3 together , then follow by pressing the power button , if lucky formatting process will take place .
But the goddess Fortuna sometimes not on our side , FUA process failed , try formatting 4 fingers is not completed , or the format is ok / finish but still contact retailer , then the action taken is :
1 . replace ic flash FL1 ( D316 ) , because user data area is located in the chip .
2 . pray and trust ........
Shown slama nokia + / - 1 min
Flashing course , this condition because of the lack of data corruptnya or variants of software / language packages ( PPM ) on hp .
Shown noki continue with the lights off or perform nokia keypad 4x
1 . use FUA features 7x if lucky to bring hockey .
2 . if still no hockey , reflow / reball or replace ic flash FL1 ( D316 ) because this chip is user data area .
3 . UPP is again unlucky when hit , heat the / reprint or replace UPP with the same version , then flash again .
60 RESTART SECONDS after booting
Bluetooth module problematic possibility .
PERFORM ERROR MESSAGE
Like the apps appear closed or system error indicates a damaged or corrupted files on drive C ( LFFS ) , this case is often caused by not kompatiblenya third -party applications installed on hp , applications that have been installed this error come running when the phone starts booting .
Format user area or * # 37370 # often resolve this case , but when the fateful day had to be flashed again , was the fateful day , the mood all night , had still failed to re flashed difull first erase then flash back again , plus frantic mood , when conditions hp still the same , it was already malem work there is not colorable .
Ic flash FL1 ( D316 ) area where user data is stored , is the most likely cause of the failure of the format user area , ic RAM is a second possible cause of the failure of the FUA .
CHARACTERISTICS OF RAM / SDRAM PROBLEM
- LCD blink / white screen for about 30 seconds .
followed - white screen keypad lights , keypad lights extinguished hp too .
- flashing failed to get into local mode ( manual power ) .
closed - apps .
Characteristic 2 Zokus problem
Component is located near conektor battery that serves to regulate the output current from the battery to the phone , by any other name Auxiliary Energy Management is responsible for managing the flow and battery sensor , causing damage to the components
Phone can not live with the output current is normal because the symptoms do not fit the white screen display / LCD blink , the phone does not work and can only nokia of these components .
Post a Comment