[General Topics] Tarasantan:
My hardbrick incident

I had a mediatek phone few years back.I found in some website or somewhere else the word "root" and benefits of rooting an android device.So I searched the internet and found several apps to root android phone.I found a chinese app called vroot.I ran the app and successfully rooted my phone.So the es file explorer app now does not bother me to activate root explorer feature.I navigated many system directories where I could not go in past without root.I deleted the framework-res.apk file from the /system/framework folder.Then all the apps on my phone just started to close.I got a feeling that I had done something wrong by deleting that file and if I rebooted now my phone would never boot again.But I still rebooted my phone with the hope that everything would be all right after the reboot.But the feeling became true and my phone never booted.I visited many local phone repairing stores but could not get my phone repaired.I thought this is not fair,all the hardwares within my phone were all right,it was just a software problem but still I had to throw my phone away because the local phone shops could not repair it.I disagreed that and kept my phone safe.I managed to get my parents to buy me another phone.Few months after I rooted that phone as well and this time a knew the importance of the system files.So I did not ever tried to delete any of the system files again.But as I had seen in the system tuner app that changing the lines in the build.prop file can make your phone faster.I changed probably the dalvik.vm.heapsize parameter to a much lower value from within the system tuner app.And I rebooted the phone and this time I faced the pain again,loosing the phone,listening to the bad comments of my sister,mother and father.Again no local phone repairing shop can repair it although all the hardwares in my phone were perfectly ok.I again disagreed to the choice of throwing the phone away.Few months after I got a Laptop.Then I tried to search about repairing the last phone.I found that these problems are very common in the internet although very rare to all the local phone repairing shops.I downloaded the entire rom of my device and flashed the rom by following each provided instruction.I learned about the sp tools program in the process.I proved to my family that I did not break my phone,it was just a software problem.I leaned about making back ups of the whole rom using sp tools and mtk droid tools programs.I learned about custom recovery and how to make a cwm recovery using the sp tools and mtk droid tools.I made one cwm recovery with mtk droid tools and sp tools and flashed it using the sp tools.I learned about custom roms.I found a custom rom and the guide to port it for my device.I learned about dsixda's Android Kitchen from the guide.I successfully ported the rom for my device but could not flash it using the cwm recovery that I made with sp tools and mtk droid tools.The solution was to get a latest working twrp or philz recovery using magic twrp program or magic philz program.So I got a latest working twrp using magic twrp program.I flashed the rom I previously made successfully.Meanwhile I found some where about the word "hardbrick" in which situation my phone would respond to nothing no physical button not even charger,and I would not be able to flash my back up rom from the computer anymore.I did not believe in that.I thought how was it possible whenever my phone would not boot I would always be able to flash the backed up rom using sp tools.So I found android to be non breakable at the software level.I also successfully downloaded and flashed the stock rom of my first soft bricked phone.

Few months after I had a phone named LYF F1 but this time it was a qualcomm phone.Before even getting the phone in my hands I planed to get a backup of the stock rom using the sp flash tools and mtk droid tools.Now when I got the phone in my hands I did as I planed.But mtk droid tools could not identify the phone.I wondered what was happening.After searching the internet I found qualcomm phones can not be backed up using sp tools and mtk droid tools these tools are for mediatek devices.So I searched the internet for few days in hope that I would found a way to backup my qualcomm phone.I found only one video tutorial to backup any non-rooted qualcomm phone using qpst tools otherwise there were many back up solutions if the phone is rooted.I tried to root my phone using almost each and every provided apps in the internet but failed,and also the back up method for the non-rooted qualcomm phones also failed.I searched the internet to found the stock but I failed.Then I downloaded some custom recoveries made for other devices with same cpu.By following some post at some where I tried to port it for my device,but again porting the recovery needed me to have my stock recovery.I thought if I could only flash the downloaded recovery and the recovery worked then I would get root access and I would be able to back up my stock rom.But the only way to flash the downloaded recovery to my qualcomm phone was to use the fastboot commands.But computer can recognise my device with the command "fastboot devices" but any other fastboot command just failed with an error remote device unknown command.Few weeks after I found the stock of my phone in the internet with someone's help.So I downloaded the whole rom,ported the recovery successfully and flashed it using the provided qcmdl program by replacing the stock recovery from the stock rom's folder with the twrp recovery.Then I got root in my this phone after a long wait through the twrp recovery.Now I tried to port a rom for my this phone.But I could not found a rom provided in the internet in the sense that it could be ported to any qualcomm device with same cpu.All the roms were made for a particular device and they were saying not to flash it on any other device.It was not the case with the mediatek phones that I had because I always found some roms which were provided in the internet in the sense that it could be ported to any mediatek device with same cpu and even the full guides to port the roms for my phone were also provided with each rom.I since then already ported many roms for my mediatek phones by following the guides provided with the roms.I took a rom made for the same device whose twrp recovery helped me to port my phone's twrp recovery.The phone was ZTE nubia z11 mini.The rom was mokee 7.1.2,the zip file contained boot.img,system folder,cmnlib.mbn,emmc_appsboot.mbn,file_contexts.bin,hyp.mbn,keymaster.mbn,modem.img,rpm.mbn,sbl1.mbn,splash.img,tz.mbn.Now when I flashed that rom I was thinking I had only seen system folder and boot.img before when I ported roms for my mediatek devices.So what were those other files? I thought they would probably make the rom work better.There were no informational file neither inside that zip file nor at their website which could suggest me what those other files were and what could happen to my device if I flash them.I flashed the rom successfully through twrp and rebooted into system.After few moments I saw my phone yet had not started to boot.I pressed the power button for few seconds and there was no response,I got a thought that my phone has hardbricked.So I tried again and again to power it on but my phone was really hardbricked.The fact that I refused to accept when I was working with roms for my mediatek devices,just came in reality.My phone would not respond to anything not for any physical button,not for charger,I could not restore the stock rom from my computer.I searched the internet day and night and tried almost each provided method and programs to restore the stock rom from my computer or from sd card but each of the methods and programs failed.Fortunately I found a fact in many places from other users in the internet that in a hardbrick situation if my phone is under warranty then service centre would repair the phone with minimum cost or without any cost at all.I send the phone to the LYF care and was thinking what did I do wrong when flashing the rom,which of the files in the zip file caused this.I searched the internet to know what are the exact work of those partition files but could not found what I was looking for,I tried my best to know the exact file with in the zip for which my phone was hardbricked,but I failed to know that.LYF service centre was saying that they had found some trace of liquid in the phone which had caused my phone to be dead and I have to pay a huge amount almost the actual price of my phone to get it repaired under warranty,I knew this was not true.So I contacted higher LYF consumer services to know them that my phone was never near any liquid so that my phone could have been harmed by it,they took the phone from the service centre and checked again,they now said some different reason and increased the amount to be paid to get my phone repaired under warranty.So I have to pay a huge amount to get my phone repaired,I do not know which of the files or the folders within the zip file caused that hardbrick,I have not been able to sleep well for last one month,and I have completely lost all faith on myself to flash anything in my phone,listening bad comments from my parents.Yeah that's my hardbrick incident.