Because crowds keep sending me PMs about their blocked devices here is tutorial how to fix it:
SEND YOUR PHONE TO REPAIR SERVICE. YOU NEED A NEW MAINBOARD.
lozohcum said:
Because crowds keep sending me PMs about their blocked devices here is tutorial how to fix it:
SEND YOUR PHONE TO REPAIR SERVICE. YOU NEED A NEW MAINBOARD.
Click to expand...
Click to collapse
If i relock bootloader and go back to stock, will this regain me warranty?
It may give you big chance that they will take it to warranty.
lozohcum said:
It may give you big chance that they will take it to warranty.
Click to expand...
Click to collapse
Im sending it in after hollidays ( approx 2 weeks, still need music on the plane ) and I'll let you guys know.
No need fo dat.
There must be a better solution
Hi lozohcum,
Please can you explain how this problem comes about further for us. At the moment I am failing to see why this has to be the only solution.
I'm no expert but have been messing around with this sort of thing for years and I have never come across something that cannot be fixed through a software hack. The only thing that comes close is the S4's flash counter - and users are only speculating that it is some sort of hardware counter, there are work arounds to avoid increasing it and seasoned devs such as ChainFire[pretty sure it was him] say that it will be reversible. Now if all that is correct I can't see Sony implementing something such as this - that can't be undone on a older and much cheaper device.
Also, I have read your post about how dev's should avoid it from happening while building their ROMs but it didn't explain why this makes it irreversible.
So, like I have asked - please explain to us whats going on that there is no way we can fix this. I feel like there must be a way!
Kind regards
Jono
PS: Taking my friends Xperia J into the service centre tomorrow
JonoIrwinRSA said:
Hi lozohcum,
Please can you explain how this problem comes about further for us. At the moment I am failing to see why this has to be the only solution.
I'm no expert but have been messing around with this sort of thing for years and I have never come across something that cannot be fixed through a software hack. The only thing that comes close is the S4's flash counter - and users are only speculating that it is some sort of hardware counter, there are work arounds to avoid increasing it and seasoned devs such as ChainFire[pretty sure it was him] say that it will be reversible. Now if all that is correct I can't see Sony implementing something such as this - that can't be undone on a older and much cheaper device.
Also, I have read your post about how dev's should avoid it from happening while building their ROMs but it didn't explain why this makes it irreversible.
So, like I have asked - please explain to us whats going on that there is no way we can fix this. I feel like there must be a way!
Kind regards
Jono
PS: Taking my friends Xperia J into the service centre tomorrow
Click to expand...
Click to collapse
I'll try answer it.
the custom rom trigger sony's security system and lock the phone. you need to flash the security system partition to fix it. the stock rom tft bundle doesn't have the image file needed to flash the security partition. thus, reflash a stock rom won't fix it. sony's security system is also very secure and at this time no one is able to hack it.
S4's flash counter - and users are only speculating that it is some sort of hardware counter, there are work arounds to avoid increasing it and seasoned devs such as ChainFire[pretty sure it was him] say that it will be reversible. Now if all that is correct I can't see Sony implementing something such as this - that can't be undone on a older and much cheaper device.
Click to expand...
Click to collapse
samsung have similar security system on their galaxy phone but it relatively not as secure as sony's. on samsung device, the security partition can be modified simply by bmtunlock tool. nevertheless, in the case of sony devices, no one know how to modify sony's security partition.
EDIT: if you're on stock rom, you can dial this code to get your lock status *#*#7378423#*#* . there's a 'simlock.ta' file in sony's tft bundle and it might related to how simlock still work after phone got locked. you can try to remove it from the tft bundle and reflash your stock rom and see what'll happen. i think it's worth to try.
Thanks for the info kurotsugi! Lock status = full lock and I've flashed it about 20 times with different roms in different ways. This one isn't coming back
I hope someone comes up with a solution soon. There must be many people with the same problem. Also I hope the issue gets stickied a bit more - I'm not blaming anyone but myself, I know the dangers of flashing, however I never knew of the issue until it was too late.
Jono
Sent from my GT-I9500 using XDA Premium 4 mobile app
kurotsugi said:
I'll try answer it.
the custom rom trigger sony's security system and lock the phone. you need to flash the security system partition to fix it. the stock rom tft bundle doesn't have the image file needed to flash the security partition. thus, reflash a stock rom won't fix it. sony's security system is also very secure and at this time no one is able to hack it.
samsung have similar security system on their galaxy phone but it relatively not as secure as sony's. on samsung device, the security partition can be modified simply by bmtunlock tool. nevertheless, in the case of sony devices, no one know how to modify sony's security partition.
EDIT: if you're on stock rom, you can dial this code to get your lock status *#*#7378423#*#* . there's a 'simlock.ta' file in sony's tft bundle and it might related to how simlock still work after phone got locked. you can try to remove it from the tft bundle and reflash your stock rom and see what'll happen. i think it's worth to try.
Click to expand...
Click to collapse
thanks @kurotsugi
Flashtool skip simlock.ta file while flashing btw
lozohcum said:
thanks @kurotsugi
Flashtool skip simlock.ta file while flashing btw
Click to expand...
Click to collapse
It's (i think) not in the TA partition, because I had a TA backup from my phone and it didn't unlock again after restoring it.
Out of curiosity, is there way to brick this device to stage that for example warranty service can`t find out that it is self-inflicted?
Surely, flashing a bootloader not intended for the device is the best way to brick it?
i will do in that way :
flash engeniereng bootloader
flash a rom not suitable for your device ( ex. rom for 9200hk )
if still works, flash wrong pit file or modified wrong one )
Why would someone do that anyway???
XxM4tzexX said:
Why would someone do that anyway???
Click to expand...
Click to collapse
I can tell you why someone would do that. This is purely hypotethical but here is one reason. Let´s say that you have rooted your device and lost your warranty. After that your camera starts to make buzzing noise and focusing don´t work. ie. this case: http://forum.xda-developers.com/galaxy-s6/help/galaxy-s6-camera-randomly-makes-loud-t3123724
Now you want to get that camera fixed for warranty, but they don´t accept it because Knox is tripped. But now if whole phone is bricked and be sent to warranty service, they have no other choice but flash stock firmware and untrip Knox and device will gain full warranty again. Or that is my theory anyway. I mean sometimes these devices just stop working maybe due faulty motherboard or something similar. Please remember this is totally hypotethical...
PeK_m said:
I can tell you why someone would do that. This is purely hypotethical but here is one reason. Let´s say that you have rooted your device and lost your warranty. After that your camera starts to make buzzing noise and focusing don´t work. ie. this case: http://forum.xda-developers.com/galaxy-s6/help/galaxy-s6-camera-randomly-makes-loud-t3123724
Now you want to get that camera fixed for warranty, but they don´t accept it because Knox is tripped. But now if whole phone is bricked and be sent to warranty service, they have no other choice but flash stock firmware and untrip Knox and device will gain full warranty again. Or that is my theory anyway. I mean sometimes these devices just stop working maybe due faulty motherboard or something similar. Please remember this is totally hypotethical...
Click to expand...
Click to collapse
Dark ideas! I like it!
I bricked my G920F trying to get back to stock-rom. Nothing would work, Odin failed time after time (cm.bin). I could flash TWRP and used ADB to get back to stock-recovery, connected to smart-switch and performed emergency restore. Failed again.
I took it to a Samsung servicepoint (talking about Holland) and they immediatly found the custom flag. Phone wil be send over to Samsung now and, according to the lady at the servicepoint, Samsung does not even check. They just reflash it and send it back under full waranty. All I can do now is hoping she is right....
Still figuring out why everybody but me can restore a bricked phone through ODIN.
I've looked through the forums to identify a similar problem to mine in hopes I can resolve this issue but I've not found one. So here's my problem.
I have a UK Galaxy S7 running on the 6.0 firmware that came with the phone when it first released (Yes I know it's very old and should have updated along the way but I had plans to root and install customs at some point which obviously didn't happen). The phone is unrooted and the stock rom is the XEU version with Multi-CSC (according to recovery)
The phone was running fine until a few days ago when all of a sudden it shut off and wouldn't power on via the power button. So I pressed and held Home + Volume Down + Power. The green screen appeared and selected Volume Down to restart the device (as you do in odd situations like this).
PHONE IS NOW STUCK IN BOOTLOOP!!!
I have tried various means (not including flashing) to get the phone to boot to the home screen with no success. I have not performed a factory reset from recovery because I have various data, including pictures, music and other software on the internal storage which I wish to keep and not lose. The phone is still under warranty so I can take it to a Samsung repair outlet to get them to fix it for me but due to data privacy or whatever, they have to format it clean to then install the most recent firmware.
I've been scouring the forums for help on flashing OTA updates which retain data on phone whilst possibly allowing my phone to boot into the home screen so I can access my data. Is such a thing possible?
Any help would be greatly appreciated.
You can flash the latest firmware without losing data (as long as the hardware is not faulty) by downloading it from either sammobile, updato.com or using the samfirm tool here on XDA (Fastest option)
Then extract the firmware and add all 4 parts to ODIN 3.12.7 (Do not use ODIN 3.13.1 unless you want to flash BTU Oreo 8.0)
AP << (Takes quite a long time to add, be patient as ODIN will look frozen)
BL
CP
HOME_CSC
If you use CSC instead of HOME_CSC it will wipe the device after the flash, HOME_CSC will not wipe it
Put the phone into download mode (Home & Power & Volume Down)
Connect to PC USB and hit start on ODIN
Wait for the flash to complete (It can take quite a while) and the phone should hopefully boot back into Android
Thank you for the quick response.
It's imperative I get this right and ensure I've understood your reply correctly.
I have downloaded the following:
SM-G930F_1_20180417125627_cz5yqc22v0_fac - from SamFirm as it was much quicker like you said.
Odin3+v3.12.7 - This particular version was quite difficult to get a hold of. Various sites redirecting me to various pages without a direct link to download but I hope that is the correct one.
The firmware zip contains the following files:
AP_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship_meta.tar -------1
BL_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship.tar -------2
CP_G930FXXU2DRB6_CL648265_QB8952207_SIGNED.tar -------3
CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar
HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar -------4
I have labelled the files 1-4 in the order of flashing/installation (I presume?)
I will also follow your instruction of flashing HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar as this will NOT wipe any existing data on the phone?
Will following the above steps act as an upgrade to the phone and not wipe apps/pictures etc in the internal storage?
Have I missed out any other steps?
Cassie` said:
Thank you for the quick response.
It's imperative I get this right and ensure I've understood your reply correctly.
I have downloaded the following:
SM-G930F_1_20180417125627_cz5yqc22v0_fac - from SamFirm as it was much quicker like you said.
Odin3+v3.12.7 - This particular version was quite difficult to get a hold of. Various sites redirecting me to various pages without a direct link to download but I hope that is the correct one.
The firmware zip contains the following files:
AP_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship_meta.tar -------1
BL_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship.tar -------2
CP_G930FXXU2DRB6_CL648265_QB8952207_SIGNED.tar -------3
CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar
HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar -------4
I have labelled the files 1-4 in the order of flashing/installation (I presume?)
I will also follow your instruction of flashing HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar as this will NOT wipe any existing data on the phone?
Will following the above steps act as an upgrade to the phone and not wipe apps/pictures etc in the internal storage?
Have I missed out any other steps?
Click to expand...
Click to collapse
Almost, you must flash all 4 files at the same time, load them all into ODIN before hitting start, doesn't matter which order you load them in as long as they are all loaded before flashing
And you are correct with the rest, HOME_CSC will not wipe anything, and yes it will act as an upgrade although it is a full ROM you are flashing, to you the user, it will appear exactly the same as an upgrade as long as you use HOME_CSC
No other steps needed
I have loaded all 4 files as seen in the screenshot however, after clicking on Start, about 5 or so minutes later, it says FAIL in the first box above where it initially said RECOVERY. It's stopped and not done anything else.
I'm not sure what to do here.
I've also added a shot of the top left of odin screen
Cassie` said:
I have loaded all 4 files as seen in the screenshot however, after clicking on Start, about 5 or so minutes later, it says FAIL in the first box above where it initially said RECOVERY. It's stopped and not done anything else.
I'm not sure what to do here.
I've also added a shot of the top left of odin screen
Click to expand...
Click to collapse
Yea it's failed, you can close ODIN and disconnect now
You can try doing it again, but that should have worked, you could try downloading the latest 6.0.1 ROM and flashing that the same way first, it looks like your bootloader is version 1 where this ROM is version 2 as shown by the S2 number in the middle of the firmware version
*Detection* said:
Yea it's failed, you can close ODIN and disconnect now
You can try doing it again, but that should have worked, you could try downloading the latest 6.0.1 ROM and flashing that the same way first, it looks like your bootloader is version 1 where this ROM is version 2 as shown by the S2 number in the middle of the firmware version
Click to expand...
Click to collapse
I've gone to https://updato.com/firmware-archive-select-model?record=0DB04AD4C34211E69215FA163EE8F90B
From there I've selected the most recent 6.0.1 ROM which is dated 4th December 2016. Problem is that the download is EXTREMELY slow and I have no idea how to use SamFirm to download that particular ROM.
I guess all I can do now is play the waiting game and repeat the steps with the 6.0.1 ROM once it's downloaded.
Thank you for your responses and I will post back here once the download has finished.
Cassie` said:
I've gone to https://updato.com/firmware-archive-select-model?record=0DB04AD4C34211E69215FA163EE8F90B
From there I've selected the most recent 6.0.1 ROM which is dated 4th December 2016. Problem is that the download is EXTREMELY slow and I have no idea how to use SamFirm to download that particular ROM.
I guess all I can do now is play the waiting game and repeat the steps with the 6.0.1 ROM once it's downloaded.
Thank you for your responses and I will post back here once the download has finished.
Click to expand...
Click to collapse
Yea unfortunately all alternatives other than samfirm tool are slow, and samfirm only downloads the latest ROM
Judging by the bootloader version and the ROM version you have chosen, if this also fails, then I would assume a hardware failure
The only other thing I could suggest if this doesn't work, is to pick an older version of ODIN to flash the older firmware, ODIN 3.11.1 was used for MM 6.0.1 ROMs if I'm remembering correctly
https://forum.xda-developers.com/showthread.php?t=2711451
or
https://odindownloader.com/download/odin3-v3-11-1
I've restarted the device and it said An error has occurred while updating the device software use the emergency recovery function.
I attempted to reboot the phone a couple of times to get into recovery and I was successful. I now see the the Bootloader version is now 2 as opposed to 1. After seeing this I attempted to flash version 7 as initially suggested yet it did not work.
I'm not sure how Bootloader changed from 1 to 2 and is still failing to flash in odin. I am still waiting for the 6.0.1 ROM to download, fluctuating between 16-19 hours as of writing this response. Once it's ready I'll try and load up odin 3.11.1 as a second solution and try 6.0.1, even though Bootloader says 2.
Cassie` said:
I've restarted the device and it said An error has occurred while updating the device software use the emergency recovery function.
I attempted to reboot the phone a couple of times to get into recovery and I was successful. I now see the the Bootloader version is now 2 as opposed to 1. After seeing this I attempted to flash version 7 as initially suggested yet it did not work.
I'm not sure how Bootloader changed from 1 to 2 and is still failing to flash in odin. I am still waiting for the 6.0.1 ROM to download, fluctuating between 16-19 hours as of writing this response. Once it's ready I'll try and load up odin 3.11.1 as a second solution and try 6.0.1, even though Bootloader says 2.
Click to expand...
Click to collapse
Your ODIN screenshot looks like it managed to flash the bootloader before it failed, so it's possible you are going to need to use a version 2 ROM from now on, I have the same phone, XEU G930F and it is running Bootloader version 2 (Running the BTU Oreo 8.0 stock ROM)
But if the 7.0 Nougat ROM failed again it's looking more like a hardware issue, seems to be failing when it should be starting to flash SYSTEM (AP)
You can try flashing the 7.0 ROM section AP on it's own with ODIN 3.12.7, see if that fails immediately, if it does that's likely where the problem lies, it's not unheard of for these S7's to fail like this out of the blue, I see it maybe a couple of times a month on XDA
Only solution is to get the mainboard replaced
But yea, give 6.0.1 a shot anyway, worth a try saying as everything else has failed up to now
(Looking for mirrors for that 6.0.1 ROM, I've got it on my main machine but it is offline right now with no graphics card so I can't access any files, stuck with a laptop, I always download and save every new firmware release for this reason)
There is Samsung SmartSwitch software for Windows for the emergency firmware recovery, but it WILL wipe your phone back to factory and delete all your data (Last resort if nothing else works, although if ODIN doesn't work, I'd say hardware failure)
Right so I've managed to download the most up to date 6.0.1 ROM and attempted to flash it with ODIN V3.11.1 and it idles at the recovery.img part and fails like the previous efforts.
I'm not sure if attempting to get OREO running with the latest ODIN might work? If not then I may have to give up and do a factory reset through Samsung SmartSwitch.
It probably is a hardware failure as I had noticed the lightning bolt appearing when the phone is off whilst plugged in the charge, it take about a minute or so for the percentage bar to appear, usually it was about 2 seconds before this disaster occurred.
Cassie` said:
Right so I've managed to download the most up to date 6.0.1 ROM and attempted to flash it with ODIN V3.11.1 and it idles at the recovery.img part and fails like the previous efforts.
I'm not sure if attempting to get OREO running with the latest ODIN might work? If not then I may have to give up and do a factory reset through Samsung SmartSwitch.
It probably is a hardware failure as I had noticed the lightning bolt appearing when the phone is off whilst plugged in the charge, it take about a minute or so for the percentage bar to appear, usually it was about 2 seconds before this disaster occurred.
Click to expand...
Click to collapse
Worth a try flashing Oreo, BTU on samfirm tool will give you it for the G930F
If you're seeing problems with the charging now, you might get lucky and find the USB port is the only thing needing replacing, but if you send it off for repair it's unlikely even if that is the case that they won't just charge you for a new mainboard, you can likely get USB ports from eBay but opening the S7 isn't as straight forward as the back is glued on for IP68 water resistance and needs a heatgun to remove, not sure if anything else like the screen needs removing for USB, I've not opened mine
You've tried a new USB cable and a different PC too ?
*Detection* said:
Worth a try flashing Oreo, BTU on samfirm tool will give you it for the G930F
If you're seeing problems with the charging now, you might get lucky and find the USB port is the only thing needing replacing, but if you send it off for repair it's unlikely even if that is the case that they won't just charge you for a new mainboard, you can likely get USB ports from eBay but opening the S7 isn't as straight forward as the back is glued on for IP68 water resistance and needs a heatgun to remove, not sure if anything else like the screen needs removing for USB, I've not opened mine
You've tried a new USB cable and a different PC too ?
Click to expand...
Click to collapse
The charging issue occurred immediately when the phone shut off by itself and wouldn't power on conventionally. The phone is still under warranty so if the Samsung SmartSwitch software is unable to recover the phone then I will take it to the repair center and have them fix/replace it. If it's a case of undoing the glue and whatnot then I'd rather they give me a replacement.
I did change the USB cable to a different one, and I've attempted to flash the 2 different ODINS with the 2 different ROMS on a laptop as opposed to the desktop I was using. Still fails at the recovery.img part of ODIN.
I'm going to try Samsung SmartSwitch now and see if this will give it some life. If THAT doesn't work then it's 100% hardware issue and my data was lost to begin with.
Considering both versions of ODIN didn't work with either ROM, I don't think I'll be looking for the BTU version of OREO to attempt to install with. If there's a direct download that's quick I might but I think I'll attempt to Emergency Recover through the Samsung tool.
I want to thank you plenty for your help and knowledge on this. It certainly has been helpful and given me better understanding of the problem I'm facing and potential solutions. I have a feeling that the SmartSwitch recovery won't work either and still be posting back here hahaha.
OK I've got bigger problems on my hands now.
SmartSwitch and Kies both say "SM-G930F" does not support initializing. Please contact our service center.
I've already inputted my serial number and it gives me the same message on both programs. When I called up customer support they said my warranty is till the end of May this year.
Would the service center be able to solve this problem?
Cassie` said:
OK I've got bigger problems on my hands now.
SmartSwitch and Kies both say "SM-G930F" does not support initializing. Please contact our service center.
I've already inputted my serial number and it gives me the same message on both programs. When I called up customer support they said my warranty is till the end of May this year.
Would the service center be able to solve this problem?
Click to expand...
Click to collapse
Yea I'd get it repaired under warranty asap then if it runs out soon, they will most likely replace the mainboard I'd say, which means 100% data loss as the storage is on a chip on that board, or might even send you a new S7
Really does sound like hardware failure if all of these recovery options have failed, just keep quiet about what you've done to try and fix it, just act dumb and say it won't turn on or they could claim you nulled your warranty messing with ODIN
And no probs, that's what XDA is all about Let us know how the repair goes and buy a MicroSD card to save your important files to this time so you don't lose anything if it happens again
*Detection* said:
Yea I'd get it repaired under warranty asap then if it runs out soon, they will most likely replace the mainboard I'd say, which means 100% data loss as the storage is on a chip on that board, or might even send you a new S7
Really does sound like hardware failure if all of these recovery options have failed, just keep quiet about what you've done to try and fix it, just act dumb and say it won't turn on or they could claim you nulled your warranty messing with ODIN
And no probs, that's what XDA is all about Let us know how the repair goes and buy a MicroSD card to save your important files to this time so you don't lose anything if it happens again
Click to expand...
Click to collapse
I had an SD card inside with all my pictures I took whilst in Japan (Thank GOD!). I took it out when this issue arose to avoid potential data loss there.
As far as ODIN is concerned, warranty still appears intact but yes I'll keep hush hush when I'm there. I believe they said they'd give me a refurbished S7 if they couldn't reflash it there.
Cassie` said:
I had an SD card inside with all my pictures I took whilst in Japan (Thank GOD!). I took it out when this issue arose to avoid potential data loss there.
As far as ODIN is concerned, warranty still appears intact but yes I'll keep hush hush when I'm there. I believe they said they'd give me a refurbished S7 if they couldn't reflash it there.
Click to expand...
Click to collapse
Yes, ODIN will not void warranty if you only flash stock, but telling them you used ODIN might, it's not a tool meant for us, it's Samsung's internal flashing tool not meant to be leaked online, sometimes they'll use any reason to blame you and not have to pay out / replace it so yea best not say anything other than official recovery methods suggested by Samsung themselves, if anything at all, I'd just say I didn't do anything, an OTA update came through and it never rebooted or something
Good job with the pics, I don't save any media to the phone itself, I create folders on the SDCard and move it over if I can't have it save there automatically, that way wiping the phone is nothing but a pain to set back up again, nothing actually lost
*Detection* said:
Yes, ODIN will not void warranty if you only flash stock, but telling them you used ODIN might, it's not a tool meant for us, it's Samsung's internal flashing tool not meant to be leaked online, sometimes they'll use any reason to blame you and not have to pay out / replace it so yea best not say anything other than official recovery methods suggested by Samsung themselves, if anything at all, I'd just say I didn't do anything, an OTA update came through and it never rebooted or something
Good job with the pics, I don't save any media to the phone itself, I create folders on the SDCard and move it over if I can't have it save there automatically, that way wiping the phone is nothing but a pain to set back up again, nothing actually lost
Click to expand...
Click to collapse
I'm going to give flashing one last try.
I am currently downloading Android 8.0.0 for United Kingdom (BTU, NOT XEU). I have to head to work in a few minutes. When I get back I'll attempt to flash that without BootLoader as that will change it to version 3 and you can't downgrade from that from what I've read here and there. If that fails then it's off to the repair center. If it's some sort of hardware failure then it won't flash regardless what stock rom/ODIN version I'm using.
Not sure if BTU update with home CSC will retain my data (assuming it works)
Cassie` said:
I'm going to give flashing one last try.
I am currently downloading Android 8.0.0 for United Kingdom (BTU, NOT XEU). I have to head to work in a few minutes. When I get back I'll attempt to flash that without BootLoader as that will change it to version 3 and you can't downgrade from that from what I've read here and there. If that fails then it's off to the repair center. If it's some sort of hardware failure then it won't flash regardless what stock rom/ODIN version I'm using.
Not sure if BTU update with home CSC will retain my data (assuming it works)
Click to expand...
Click to collapse
Your CSC will remain XEU as it is Multi-CSC containing BTU, and BTU contains XEU, I'm running it now with BTU firmware & XEU CSC
Bootloader for this Oreo 8.0 BTU firmware is still 2, with it being a new Android version you'll need to flash the BL too anyway
*Detection* said:
Your CSC will remain XEU as it is Multi-CSC containing BTU, and BTU contains XEU, I'm running it now with BTU firmware & XEU CSC
Bootloader for this Oreo 8.0 BTU firmware is still 2, with it being a new Android version you'll need to flash the BL too anyway
Click to expand...
Click to collapse
I've had no luck flashing it with Oreo. It's definitely going to the repair centre. Such a shame.
I'm very grateful for your time and help with this. I will report back this weekend with the results of what the repair centre will do regarding the device. Don't like to leave a thread without an end result.
Many thanks again!
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
hello....
Recently i went to authorized service center for downgrading miui 12 to 11.....and the engineer told me there is a risk of failure during process which is not recommended,there is a 50/50 % chance of it....wanted to know is this true cause also went to same center before for battery issue and he downgraded it without any giving above reason....only this time i went directly and told him to downgrade....
thnx
advice please
ganeshg44 said:
advice please
Click to expand...
Click to collapse
It is not a myth by any means. All android devices (especially the ones shipped with MIUI) come with something called Antirollback. It is a protective index (or counter, depending on your understanding of android) that prevents you from downgrading your OS for security reasons.
Now it is not absolute, meaning you can probably downgrade 1 version successfully, More than that and your device can get bricked. If you really want to try your luck yourself, you can download the Fastboot firmware and try flashing it, although the probability that it'll work is less than 50%. Go to your device specific Forum and ask there first.
ok thnx.......don
Slim K said:
It is not a myth by any means. All android devices (especially the ones shipped with MIUI) come with something called Antirollback. It is a protective index (or counter, depending on your understanding of android) that prevents you from downgrading your OS for security reasons.
Now it is not absolute, meaning you can probably downgrade 1 version successfully, More than that and your device can get bricked. If you really want to try your luck yourself, you can download the Fastboot firmware and try flashing it, although the probability that it'll work is less than 50%. Go to your device specific Forum and ask there first.
Click to expand...
Click to collapse
k thnx......dont want to take chance......probably will get another phone instead of poco.....cause too much problems in ui.