Database Info

[WARNING] Do not partition SD card using ClockworkMod | FIXED in 3.0.2.6

As the title says, do not partition SD card using ClockworkMod or ROM Manager.​
There has been multiple bricked devices already, all after partitioning SD in CWM. The device suddenly turns off while the partitioning is in progress, and never turns on again. We do not know what causes this issue yet, but I am sure that ClockworkMod team will look into it.
Update:
Koush said:
Looking into this. I don't have a DHD but I have an idea why this is happening.
Click to expand...
Click to collapse
Update 2:
Koush said:
I have a fix ready now. I will need to release a new recovery and new ROM Manager to address this.
Click to expand...
Click to collapse
Update 3:
New ClockworkMod 3.0.2.6 and ROM Manager 4.1.0.0 are out! There has been multiple confirmations of the problem being fixed, but also ONE brick. So take the fix with a grain of salt.

Wow... Never used partitions on SDcard , but thanks for the warning.
I'm curious how the device bricked while partitioning SDCARD, though, as I don't see the connection!

have another brick here from the same reason, be aware.

MafiotuL said:
Wow... Never used partitions on SDcard , but thanks for the warning.
I'm curious how the device bricked while partitioning SDCARD, though, as I don't see the connection!
Click to expand...
Click to collapse
Easy, partition the wrong partition, iow the NAND/eMMC.

does anybody know if it affects other devices also?

MafiotuL said:
Wow... Never used partitions on SDcard , but thanks for the warning.
I'm curious how the device bricked while partitioning SDCARD, though, as I don't see the connection!
Click to expand...
Click to collapse
HOLY SHT!!!!!!!
I partitioned my sdcard thru Clockword recovery 3 months ago back then with 2.5.0.7 htc desire
it hung for 1 hour so i pulled the battery but it was paritioned rite phewwwwww..
Cant imagine if i had a bricked phone now,would prolly pee on my pants....

Darn it. I was thinking about partitioning my SDCard today but postponed it. Thanks for the information.
Are there any other known issues that the CWM might cause to the device? Last year, when I had HTC Dream, I remember reading in forums at Cyanogen that some people didn't recommend using ROM Manager. I don't know what issues it used to cause because I used Amon_Ra back then.
Anyways, thanks for the information. I won't partition the SDCard using CWM.

Ok............
This thread has been stickied by me in order to inform everybody about this situation.
Do report if you have gone through this problem only...no more thanks or OT chatter, please.
I'm in contact with the Mod team to investigate even further if this does affect any other devices as well.
Please be patient and do not pollute this thread
Cheers,
M_T_M
@jkoljo...thanks for your help on this very important matter.

Got another one here: http://www.android-hilfe.de/root-ha...t-nicht-mehr-nach-partitionierung-der-sd.html [German], thank goodness it wasn't mine

Bricked DHD
Hi There,
Had this a few days ago.
the device is indeed completely bricked, no matter what you do.
Luckily for me my HTC DHD was only 10 days old, so i went to the store and after inspection theyt gave me a new one. I must be very lucky i guess.
Thanks for the warning nevertheless.

hello. I have the same problem. it goes in the black this afternoon before I have read the forum. Is there any thing i can do to get the phone alive again. : ((

All versions of CWM ? Or is it specific to a version ?
All the best,
Sharro

We do not exactly know at this point. At least 3.0.2.5 has the problem.
There is nothing you can do to fix a brick. That is why it is called a brick.

kilavuz said:
hello. I have the same problem. it goes in the black this afternoon before I have read the forum. Is there any thing i can do to get the phone alive again. : ((
Click to expand...
Click to collapse
I believe you can still return it for manufacturer warranty. HTC phones has at least one year manufacturer. Just say to them you turn on your phone and it couldn't turn on....simplesssss

it is only 2 weeks old. : ((

Other solution
Hi guys,
I've also read somewhere, last november I think, that partitioning could be problematic. So I looked up on the internet and can recommand you what I use to partition my SDHC cards: Paragon partition manager 11 free , I used it on Win XP 32 bits without any problem with my 16gb and with my 3 other 8gb SDHC.
link: here
f.
M_T_M said:
This thread has been stickied by me in order to inform everybody about this situation.
Do report if you have gone through this problem only...no more thanks or OT chatter, please.
I'm in contact with the Mod team to investigate even further if this does affect any other devices as well.
Please be patient and do not pollute this thread
Cheers,
M_T_M
@jkoljo...thanks for your help on this very important matter.
Click to expand...
Click to collapse

Thanks
Thanks for the warning, yesterday I had considered to partition my SD ..

best would be to partition SD's via PC and to disable the partitioningfunction for the next update. I'd be bad if someone uses it again.

2-die-4 said:
best would be to partition SD's via PC and to disable the partitioningfunction for the next update. I'd be bad if someone uses it again.
Click to expand...
Click to collapse
Yep. I contacted Koush about this issue, so hopefully we get a fix (someone dare to try..? ) or it gets disabled.

I heard this from a customer so take this with a grain of salt but he told me he was an Android Developer and had heard of an interesting "trick" concerning all HTC Android phones.
These phones apparently have a SECONDARY bootloader that is completely hidden and disabled by default and that all those phones are HARDCODED to immediately enter into it the moment they get connected to a specific USB cable.
The guy was looking for the cheapest possible, well, item really, to buy and then proceed to cannibalize as a test to its' validity (he bought an old Motorola handsfree) so it seems he wasn't sure of it either.
Apparently what needs to be done is that the PLUG needs to be completely stripped and either two resistors or two capacitors (I forget which) of specific values need to be soldered to two specific lungs of the plug.
I am sorry I am being this vague but that was all the information I got from him in the matter of the couple of minutes it took him to buy the handsfree.
Perhaps there's sth to be looked into by some people better equipped than I?
EDIT: On second thought, it makes more sense if what he said was to solder A resistor/capacitor to TWO specific lugs of the plug, perhaps?
I kinda remember him saying that the plug itself doesn't even really need to lead to anywhere but it's more like the means to connecting the resistor/capacitor to those two lugs...
He also said that that's how HTC themselves un-brick bricked phones. He didn't appear to be talking just for Dev phones either.
I am sorry I really do not know any details.

Galaxy S5 Clone almost dead (OS damaged) and I can't flash. Help!

First of all, let me introduce myself. My name's Rafael and this is my 1st post in this forum. I hope humbly that you can to help me with the problem that I'll show you then:
Well. To begin, the issue is this... I am working with a telephone that's not mine. Somebody sent it to me to fix it, they said me that the phone doesn't download more apps because of "full memory". When I checked it, apparently it had the internal memory partitioned incorrectly, it said it was 16gb total storage with 7 GB available, but when I was installing some apps and went back to see the memory, it showed the Available Storage Memory with a large negative number, and it wasn't letting me install more apps. Some of the features of the phone are the following (according to MTK Droid Tools):
MTK6589 <---------(Actually it's MTK6571)
Model Name: Galaxy S5
Android Version: 4.4.4 <---------(Questionable)
Model Number: SM-G900H
Base Band: G900HXXU1ANCE
Then, to see if I could make some change, I decided to install a custom ROM, apparently for MTK6589 (at that time I didn't suspect about the horrible phone's falsehood). I wanted to see if this ROM brought the partition configured correctly. I tried to carry out the installation by the CWM Recovery from SD card. It turned out that the installation did not exceed 10% and it froze there. Then I removed the battery of the phone and inserted it again. When I try to turn it back on, it stays on the screen Mediatek. And from there, it does absolutely nothing more.
I've tried to flash back the backup that I made to the phone with MTK Droid Tools, both version 5 of SP Flash Tool as version 3, but I'm still not achieving positive results, always it throws me errors errors and more errors . I've searched all over the web, compatible ROMs for this phone, but apparently there is not anything. The only way in which (at least) it begins to flash from SPFT v5, is loading a ROM MTK6571; if not, it only throws errors. However, I've already tried, but it gave me error. It appears when the yellow bar that says Download Flash reaches 3%, and then it throws the error.
The only possible solution I see is to make a ROM (from the backup I made to the phone with MTK Droid Tools before to **** it up) installable from recovery (CWM) that is the only thing that works relatively well. And I have not reached that conclusion alone, but in bilateral agreement with an expert from another forum with who I have almost a month discussing the issue.
I really need help buddies. I am desperate because I'm a bit under pressure because I have almost a month with the phone without achieving the desired results. :crying:
Greetings and thanks in advance to any of you who want to help me.
PD: Sorry for my bad English if I committed mistakes.

Post removed

Killwish said:
Download stock firmware from http://samsung-updates.com or http://sammobile.com
And flash it via odin...
Good luck
Click to expand...
Click to collapse
Do NOT do this. None of them will work.
Your issue is that 99% of the time clones dont not have the software they claim and are never made by the company they claim they are. You could try porting a rom over that has the same chip but ill be honest. XDA doesnt really do anything with cheap knock off devices. Most people avoid them like the plague.

Sorry for my previous post..... I didn't read carefully. It's not s5 its clone....

Another way...
zelendel said:
Do NOT do this. None of them will work.
Your issue is that 99% of the time clones dont not have the software they claim and are never made by the company they claim they are. You could try porting a rom over that has the same chip but ill be honest. XDA doesnt really do anything with cheap knock off devices. Most people avoid them like the plague.
Click to expand...
Click to collapse
I was thinking about to take system.ubifs.tar and boot.img from the backup, to turn it into a bootable (installable) ROM from the recovery. Is it somehow possible?

06rafagar94d said:
I was thinking about to take system.ubifs.tar and boot.img from the backup, to turn it into a bootable (installable) ROM from the recovery. Is it somehow possible?
Click to expand...
Click to collapse
Best advise is that you can try. Like I said we dont deal with clones at all really.
Worst thing that will happen is that it wont work and you learned a lesson about clone devices.

Hopelessly stuck in a boot loop, unable to resolve. (resolved/fixed)

Hey folks I'm looking for ideas to unbrick my OPO which is permanently stuck in a boot loop. It all began last Friday while flashing the lastest CM nightly and gapps. The flash executed successfully then entered a boot loop that refuses to be resolved. I've tried formatting and wiping all pertinent partitions including /persistent, fastboot flashing different version stock images, different radios... I don't know what else to try short of j-tag to rectify. Any and all advice appreciated. TIA
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Feb. 18th, 2016 Edit:
Well I'm happy to announce that after nearly 5 months of trying different tactics I was finally able to get my handset up and running this weekend.
The technique I used was to first flash the new official Oxygen OS following the directions from the oneplus forums. From there I was able to boot-up for the first time in months, but had no connectivity. I went to settings and saw I had no IMEI showing. Realizing this, I tried using the technique Heisenberg suggested below in this thread, but again I had no success.
Then I tried the instructions in this thread (which I had tried previously with no success) http://forum.xda-developers.com/oneplus-one/general/guide-efs-partitions-how-to-lost-t3307793 and viola! I got my radio back. It took me several attempts to get bluetooth and wifi back working, with rebooting in between, but alas I was able to get all fully functioning again.
Then I re-rooted and reinstalled TWRP (unofficial 3.0), backed up everything (including firmware and EFS partitions), then proceeded to flash the latest CM snapshot, then eventually the latest CM-12.1 unofficial CAF Sultanxda that I'm now happily running!!!
Thanks again to everyone who posted trying to help me get my handset working again. Now I have two fully functioning OPO's and am very happy!!!

Odysseus1962 said:
Hey folks I'm looking for ideas to unbrick my OPO which is permanently stuck in a boot loop. It all began last Friday while flashing the lastest CM nightly and gapps. The flash executed successfully then entered a boot loop that refuses to be resolved. I've tried formatting and wiping all pertinent partitions including /persistent, fastboot flashing different version stock images, different radios... I don't know what else to try short of j-tag to rectify. Any and all advice appreciated. TIA
Click to expand...
Click to collapse
You might have a corrupt persist partition. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
Then:
Code:
fastboot erase persist
fastboot flash persist persist.img

Heisenberg said:
You might have a corrupt persist partition. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
Then:
Code:
fastboot erase persist
fastboot flash persist persist.img
Click to expand...
Click to collapse
Thanks it's greatly appreciated. I had tried this earlier with a download from another link, but tried again with your persist.img and unfortunately, it too didn't work.
This scenario that I'm currently experiencing is eerily like a common problem we had with the HD2, where over time and use NAND cells would get "stuck" and go bad. If the bad cells were located in the portion of the NAND allocated for the /system partition an unresolvable boot loop would result. To work around this developers added tools to HD2 recoveries that would allow reordering and resizing partitions so the /system partition would wholly reside in a contiguous healthy part of the NAND.
I'm wondering now if the hundreds of times I've flashed my beloved OPO has taken its toll, and created a similar situation where bad NAND cells now reside within the boundaries of my /system partition?
Anyone familiar or aware of any tools I can use from either recovery or fastboot that would allow checking the integrity of the NAND to determine if this is indeed the cause of my current dilemma or rule it out?
Again, any help or suggestions would be greatly appreciated. TIA

Odysseus1962 said:
Thanks it's greatly appreciated. I had tried this earlier with a download from another link, but tried again with your persist.img and unfortunately, it too didn't work.
This scenario that I'm currently experiencing is eerily like a common problem we had with the HD2, where over time and use NAND cells would get "stuck" and go bad. If the bad cells were located in the portion of the NAND allocated for the /system partition an unresolvable boot loop would result. To work around this developers added tools to HD2 recoveries that would allow reordering and resizing partitions so the /system partition would wholly reside in a contiguous healthy part of the NAND.
I'm wondering now if the hundreds of times I've flashed my beloved OPO has taken its toll, and created a similar situation where bad NAND cells now reside within the boundaries of my /system partition?
Anyone familiar or aware of any tools I can use from either recovery or fastboot that would allow checking the integrity of the NAND to determine if this is indeed the cause of my current dilemma or rule it out?
Again, any help or suggestions would be greatly appreciated. TIA
Click to expand...
Click to collapse
If that is the case it's the first time I've heard of it happening on this device. TWRP may have a feature like that but I'm not sure. Other than that I'm unaware of any tools of this nature.

Heisenberg said:
If that is the case it's the first time I've heard of it happening on this device. TWRP may have a feature like that but I'm not sure. Other than that I'm unaware of any tools of this nature.
Click to expand...
Click to collapse
Thanks again for responding. I'm just at my wit's end with this and out of ideas, which is why I even suggested the hypothesis in my previous post. Fortunately, I have another OPO backup, so I still have a phone, but it too is problematic. Whenever the capacitive buttons are activated I experience phantom touches of the menu button, and usually at the most inopportune time. OPO customer service is nonexistent and have insisted since I received the defective device that my problems are firmware related and refuse to investigate further. Nearly a year later and numerous updates the problem is still unresolved, which is why I took the device out of service and made it my spare.
Now with my daily driver malfunctioning I'm nearly ready to throw in the towel and give up on Oneplus altogether and get another device from a more reputable manufacturer. They've sent me several OP2 invites, that I've declined using. My horrible customer service experience with them and now two faulty devices leads me to never want to purchase their products again, no matter how affordable or feature packed they may be.
Anyhow, as previously posted, if anyone has ideas to resolve my boot loop, please chime in. TIA

Is it possible that my boot looping is being caused by a corrupt iemi partition? If so, I never backed it up, but have the number readily available from the packaging my OPO shipped in. I also have my backup OPO that I'm currently using, is it possible to clone that partition?
Any ideas on how to recover or clone my from my other device would be greatly appreciated. Basically anything to help get my daily driver back up and running would be a heaven send. TIA

Odysseus1962 said:
Is it possible that my boot looping is being caused by a corrupt iemi partition? If so, I never backed it up, but have the number readily available from the packaging my OPO shipped in. I also have my backup OPO that I'm currently using, is it possible to clone that partition?
Any ideas on how to recover or clone my from my other device would be greatly appreciated. Basically anything to help get my daily driver back up and running would be a heaven send. TIA
Click to expand...
Click to collapse
A corrupt EFS partition doesn't cause this to happen, the phone will still boot but will have no network because it has no baseband and no IMEI.

Still trying to resovle. I refuse to give up!
I'm still looking for help in resolving this bootloop issue. I refuse to give up as long as there is the slightest hope of getting it back up and working.
Being a longtime Linux user I know that by default there must be some type of logs generated in the boot-up process. I'm thinking that perhaps if I can extract the log(s) and post them maybe someone can point me in the right direction towards resolving this issue. I've noticed that after flashing back the stock recovery there is a section which contains several logs. Which do I need, where do they reside, how can I extract them from my device, and how should I repost (them) here so they can be properly deciphered? TIA

Why don't you hard brick your phone and unbrick it by flashing ColorOS ? Not joking .. You can try that .. anyhow you're facing a soft brick ..

Tried flashing with twrp 2.8.6 build instead of 2.8.7?

Sanjiv Kumar said:
Why don't you hard brick your phone and unbrick it by flashing ColorOS ? Not joking .. You can try that .. anyhow you're facing a soft brick ..
Click to expand...
Click to collapse
I thought about this as a possible solution, but the "hard unbricking guide" only contains solutions to use with various versions of Windows. Unfortunately, I have no access to a Windows computer (at least one that someone would allow me to use for the purpose of unbricking). I run Linux on my laptop and desktop, specifically Gentoo Linux ~AMD64. I haven't run Windows on any of my machines for over a decade. For the extremely rare instances where I need to use a Windows application I run it on WINE in Linux.
If someone knows how to run the ColorOS unbricking procedure on Linux, I'd be happy to try it out.
NoobInToto said:
Tried flashing with twrp 2.8.6 build instead of 2.8.7?
Click to expand...
Click to collapse
This device was already running TWRP-2.8.6 prior to getting stuck in the bootloop. Since then I've tried every version above 2.8.4, I've tried Phil's, and CWM and both the CyanogenOS and CM recoveries. All with the same result.

Bumb to bring back up this thread, now that I've resolved my problems. Hopefully it will help someone else who may be having similar issues.

SIM card not detected (anymore)

Hi,
some issues with my brand new Xiaomi Mi 4i.... I'm getting reaaaally tired of this.
My story with this phone went well for a day. Then I tried to install a french ROM and I guess I did something wrong cause my phone was hardbricked. I managed to recover from that (throught steps I couldn't really remember, I tried so many things) but when I put my SIM card on my phone, it's not detected anymore, despite working on another device (a Lumia 1320)
I read it might be an hardware issue (and not covered by warranty, which is a real shame), but some stuffs tells me otherwise :
- the card was working before the hardbrick;
- MiPCSuite is messed up: it worked perfectly before the hardbrick, but now it's considering my phone as a "mi device" (and not a Xiaomi Mi 4i), I can't backup anything because my phone "isn't up to date" (despite having installed MiUI7 to check if the issue came from MiUI6 for some reasons)... I know it's nothing really important, but it might indicate that it's software related... right ? :crying:
I took the hardbrick well because I know it was my fault, and my fault only. But now that I have this issue... I'm kinda pissed. And the fact is that I don't have any center near me, because I'm in France (explaining why I tried to install a french rom and why my english isn't the best), so if I have to send my Mi 4i back, it will cost me a lot AND I won't have my device for monthes...
If you have ANY information that could help me, I would gladly take it. Thanks !
Edit : "baseband" is marked as unknown. Guess it matters...

did you backup your EFS (EFS Backup) before flashing custom rom? if yes then try tro restore your efs with twrp (i assumed you used twrp)

Danusyakti said:
did you backup your EFS (EFS Backup) before flashing custom rom? if yes then try tro restore your efs with twrp (i assumed you used twrp)
Click to expand...
Click to collapse
My motto always has been, and I know it's a very stupid motto, "if you backup, things are going to mess up". I never backedup anything, assuming everything would go according to plan.
So no, sadly, I don't have any EFS backup (or any backup at all...). I used TWRP, but since my phone resurrected, I didn't have the guts to reinstall TWRP. If I don't have any backup, it would be useless, wouldn't it?
I'm gonna try when I'll can to redo a full factory reset + fastboot flash using MiFlash Tools. Read it worked for Xiaomi Mi4, but don't have much hope. I guess the issue relies on something else than just a ROM. ( but I might be wrong, once again I'm really not an expert and this is my first Android device ( and yeah, yeah, I was stupid ) ).

try FastBoot Flashing, open this link
http://en.miui.com/thread-112662-1-1.html
i hope it only software related, not hardware related
*btw can you do imei checkup with your phone?

Danusyakti said:
try FastBoot Flashing, open this link
i hope it only software related, not hardware related
*btw can you do imei checkup with your phone?
Click to expand...
Click to collapse
I hope the same thing than you
By IMEI checkup, did you mean verify if my MiPhone is a legit one? If yes, yeah, I tried and it's an official one.
If not, in the "Details", neither IMEI or IMEI SV are known.

poneyroux said:
I hope the same thing than you
By IMEI checkup, did you mean verify if my MiPhone is a legit one? If yes, yeah, I tried and it's an official one.
If not, in the "Details", neither IMEI or IMEI SV are known.
Click to expand...
Click to collapse
no i mean with *#06#
i you can't it meant you lost your efs, if detected just try flashing again with link above
good luck

Danusyakti said:
no i mean with *#06#
i you can't it meant you lost your efs, if detected just try flashing again with link above
good luck
Click to expand...
Click to collapse
It says "Invalid IMEI"... I flashed as your link said, but didn't work...

Well. "All I have to do" is to fix the two corrupted IMEI files. I found which ones are appropriate : mmcblk0p20 et p21.
I guess they are corrupted, I don't really know... Dunno if there is anyway to fix this, maybe by modifying the files with notepad or something like that. Really, I don't know, but I'm kinda despaired.

This might help
forum.xda-developers.com/mi-4i/help/strange-bricked-wifi-bt-radio-t3210529
This guy had the same problem.. I tired helping by using extended twrp and uploading it. He seemed to have fixed it. Try posting there

sharan.nyn said:
forum.xda-developers.com/mi-4i/help/strange-bricked-wifi-bt-radio-t3210529
This guy had the same problem.. I tired helping by using extended twrp and uploading it. He seemed to have fixed it. Try posting there
Click to expand...
Click to collapse
Thanks. Gonna try this.
Quick question : could you upload somewhere your mmcblk0p20 and mmcblk0p21 files for me to compare with mine?
Two ways to get it : with mi4i toolkit (EFS backup, it will be stored on /sdcard/efs-backup) or by following the tutoriel by magdag :
http://en.miui.com/thread-59832-1-1.html

Hi, it's me again,
I contacted the saler of my Mi 4i to ask if he knows any way to repair it or why. I was very surprised to see that the website proposed me 1) A partial refund (40%) on the websites account 2) A total refund (but the item is shipped at my cost) or 3) The same phone, half price, without the need of being reshipped.
I'm very surprised that it's covered by warranty... any ideas about that? Any chance that once I've shipped my Mi4i back, they'll ask me to pay for the replacement?

i am facing similar issue but my sim is not detecting on first slot but it is detecting on second slot
even my imei is showing correctly should is go for replacement coz i bought it few days back

If the SIM card tray is damaged (for example, a piece of plastic is chipped off or a metal plate is deformed), this can be the cause of the problem when the Xiaomi smartphone does not see the SIM card.
I had such a situation on my Mi 3. In the service center they could not find the cause of the problem, I found it myself.
I hope this information will help to somebody.

Phone is dead after flashing

Hello
I've just flashed my Philips Xenium v787 and installed an official ROM here mediafire.com/file/o91r1zl8nuvsy7u/Philips_V787_MT6753.zip but after flashing is successfully completed, i tried to turn on my mobile but it won't load up and i tried to charge it but no sign!!
Please help.

Caboz said:
Hello
I've just flashed my Philips Xenium v787 and installed an official ROM here mediafire.com/file/o91r1zl8nuvsy7u/Philips_V787_MT6753.zip but after flashing is successfully completed, i tried to turn on my mobile but it won't load up and i tried to charge it but no sign!!
Please help.
Click to expand...
Click to collapse
When you say official ROM, do you mean a stock ROM ripped and put on the internet, or a custom ROM used for customization? Does anything pop-up on the screen when you press the power button (i.e. battery indicator)?

CrafterJG said:
When you say official ROM, do you mean a stock ROM ripped and put on the internet, or a custom ROM used for customization? Does anything pop-up on the screen when you press the power button (i.e. battery indicator)?
Click to expand...
Click to collapse
I meant a stock ROM on the internet. Nothing shows up at all, tried to charge the phone and there's no sign, and then tried to get into the recovery mode using power off and volume up + down buttons and nothing happens at all. I'm afraid that my phone could be completely damaged :crying:

Caboz said:
I meant a stock ROM on the internet. Nothing shows up at all, tried to charge the phone and there's no sign, and then tried to get into the recovery mode using power off and volume up + down buttons and nothing happens at all. I'm afraid that my phone could be completely damaged :crying:
Click to expand...
Click to collapse
It sounds like your phone may be "bricked". This happens when you load a faulty recovery image onto your device, whether it's incompatible with your device, or a bad recovery. Don't fret, though, as this is sometimes fixable. A simple google search for how to unbrick an Android device delivers a wealth of results, but sometimes a device-specific search may be more relevant to your situation. Best of luck! :good:
- CrafterJG

CrafterJG said:
It sounds like your phone may be "bricked". This happens when you load a faulty recovery image onto your device, whether it's incompatible with your device, or a bad recovery. Don't fret, though, as this is sometimes fixable. A simple google search for how to unbrick an Android device delivers a wealth of results, but sometimes a device-specific search may be more relevant to your situation. Best of luck! :good:
- CrafterJG
Click to expand...
Click to collapse
Well i searched in Google and unfortunately it seems like my phone is hard bricked. However, I'm going to send it to a repair center and see what's going to happen but i feel like i most likely will end up needing to buy a new phone. Thanks anyways!

Caboz said:
Well i searched in Google and unfortunately it seems like my phone is hard bricked. However, I'm going to send it to a repair center and see what's going to happen but i feel like i most likely will end up needing to buy a new phone. Thanks anyways!
Click to expand...
Click to collapse
Somehow, what you flashed must not have been for your specific device. Flashing stuff that wasn't made for your specific device is the fastest way to hard-brick a device.
From what you posted in your first post, the file that you downloaded and flashed looks like it should be the correct firmware for your device. But, since you didn't download it from the official site for your device, the file that you downloaded may have been modified before it was posted at the place that you downloaded it from or maybe your downloaded file got corrupted or didn't download completely. A corrupted/incomplete file could result in a hard-brick.
Another thing that could have gone wrong is a faulty connection between your device and PC during the flashing process. Or maybe the battery died during flashing or during first boot. This can also cause a brick.
You might be able to repair the device yourself by replacing the motherboard. It could be cheaper than buying a new device or cheaper than the cost of repairs at a shop. Try finding a YouTube video that demonstrates how to disassemble your device to replace the motherboard. You will have to be certain that you are buying the correct motherboard for your specific device model number. After replacing the motherboard, you will have to make certain that you have the correct official firmware file and then flash that firmware onto the new motherboard.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Somehow, what you flashed must not have been for your specific device. Flashing stuff that wasn't made for your specific device is the fastest way to hard-brick a device.
From what you posted in your first post, the file that you downloaded and flashed looks like it should be the correct firmware for your device. But, since you didn't download it from the official site for your device, the file that you downloaded may have been modified before it was posted at the place that you downloaded it from or maybe your downloaded file got corrupted or didn't download completely. A corrupted/incomplete file could result in a hard-brick.
Another thing that could have gone wrong is a faulty connection between your device and PC during the flashing process. Or maybe the battery died during flashing or during first boot. This can also cause a brick.
You might be able to repair the device yourself by replacing the motherboard. It could be cheaper than buying a new device or cheaper than the cost of repairs at a shop. Try finding a YouTube video that demonstrates how to disassemble your device to replace the motherboard. You will have to be certain that you are buying the correct motherboard for your specific device model number. After replacing the motherboard, you will have to make certain that you have the correct official firmware file and then flash that firmware onto the new motherboard.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks for you reply.
Yesterday i went to a few local repair shops and one of technicians connected my phone to a charger where you get a light if your device is connected and working properly, then he told me that it's getting enough amps(ampere) to work well but it's probably going to need a software, unfortunately, they couldn't help me, as they don't have the required software for my device (Philips) and they advised me to visit the manufacturer's service center in order to solve this issue.
What I've noticed is that when i connect my phone to my laptop, i can still hear a sound like the one you get when you connect a USB to your laptop, so maybe it's not a hardware issue?
I've called my manufacturer's repair center and they mentioned that for any repair-related issues, it's going to take 3 working days to fix any issue (due to their policy). However, I'm afraid of having my data spied on/accessed if i left my phone over there and I'm really confused whether to buy a new one or just leave it to get fixed.
P.S To everyone who is trying to help me, i do really appreciate it