Database Users

[Q] SGS Problem That Nobody Can Fix?

The main Samsung Approved Service Center here in Kenya has just given up on my SGS 1900 UK Model Nov 2010, originally 2.1 firmware upgrade via KIES to Froyo 2.21 in March 2011. They have handed it back unfixed after a week. Cant find a problem like this on any forum/google. Can find one that is fixable with the resistor jig, but Samsung dealer says his jigs don't help:
1) Press power, on comes B&W Samsung GT I900 screen, then the mosaic graphic that resolves to the glowing big "S". Then it buzzes feebly. Eventually it goes black but keeps buzzing now and then. Power off works.
If you poke around trying to get it into 3 touch reset, the Menu and Back keys light up and stay lit.
2) 3 Touch reset will not work. Dunno if it ever did as never tried before.
3) Plug into USB charger, it charges fine and shows the charger icon.
4) Plug into KIES and after a lot of attempts, KIES identifies it + firmware and connects. I can see and save my contacts and it displays CONTACTS, INTERNAL SD and CALENDAR folders in KIES. No more
5) ODIN ( which I dunno how 2 use but have) sees the SGS's COM when I plug it to my comp.
6) The dealer claims to have tried to resart/reflash with Samsung jigs. He has handed it back with a "cant fix".
What the heck is going on here? Looks like I have lost a few hundred bucks and have to throw it away.
When did this start? Phone was working perfectly. Suddenly a solid red icon with large white star labelled "Web Page" appeared on home page but no such App was found in SETTINGS>ETC. In any case, "Web Page" just led me to a totally innocuous page I use all the time as a homepage on INTERNET app. A few starts and shutdowns after that ( the battery was getting low so swx'd on and off like 3 times over an hour), it just went into (1) above.
Phone is STOCK, no mods, no reflashes,no rooting etc
Thanks
Peter in Darkest Africa

if odin can 'see' you handset, have you tried flashing the ROM again? find a stock froyo rom from one of the threads here in the general section (click here) or download from samfirmware.com .
Once you have the rom files, kill all the KIES tasks using the task-manager in windows. Get your phone into download mode by pressing volume down+menu button+power button until you get the yellow screen showing the android working. then open odin 1.7 and connect your handset. once odin connects, click on the buttons for PDA,PHONE and CSC in odin and browse to the appropraite file which you've download in the rom. also click on the PIT button, browse to the odin folder and select the 512.pit file. Once this is done, check the main odin window to make sure the check-box next to 're-partition' is checked. click start and it should flash the new firmware for you.
Disclaimer: I do not take responsibility for any harm that may come to your phone during the flashing process. The instuctions above are accurate but are to be performed at your own risk.

flash Darky Rom 10.1 with JVO Modem . Best GPS i´ve ever had, and my GPS was really bad.

frostygenius said:
if odin can 'see' you handset, have you tried flashing the ROM again? find a stock froyo rom from one of the threads here in the general section (click here) or download from samfirmware.com .
Once you have the rom files, kill all the KIES tasks using the task-manager in windows. then open odin and connect your handset. once odin connects, click on the buttons for PDA,PHONE and CSC in odin and browse to the appropraite file which you've download in the rom. also click on the PIT button, browse to the odin folder and select the 512.pit file. Once this is done, check the main odin window to make sure the check-box next to 're-partition' is checked. click start and it should flash the new firmware for you.
Disclaimer: I do not take responsibility for any harm that may come to your phone during the flashing process. The instuctions above are accurate but are to be performed at your own risk.
Click to expand...
Click to collapse
@frostygenius
I don´t think that your instrunctions ARE accuarate. You don´t even mention that he has to be in Download mode if he wants to use Odin. Also you advise to connect phone right after opening Odin and than insert the files, but some versions of Odin are known that they malfunctioning if you do this in this order, You should first insert files and set odin and after that plug in your phone.
And if he claims that he is on stock since bought the phone, so maybe he never used it before.
@peterg123
I´m not exactly following what happens to your phone. If I understand correctly the Samsung released defective ROM via KIES and after a week turn it down? But you already updated and now your phone is broken? If yes, I think that Samsung service center should repair your phone or if its serious damage than even replace it.
Is the phone able to boot-up and work properly? Is your recovery mode and/or download mode working? If the download mode (use 3-button combo - VolDown+Home+Power) is working then you can try recover on your own, but be careful, dont do anything before you are sure that you know what you are doing. You can go through this post before start [HOWTO] [REF] [FAQ] [Guides] [Tutorials] Flash/Root/ADB/ROM [MUST READ!].
Also go through the forum or samfirmware.com and find your official version of rom (Eclair 2.1) to be sure that you can anytime revert to this one because of warranty.
EDIT: Also can you please post some photos or video showing what happens to your phone?

Ok, I dunno if this is gonna help but I had a very similar issue when I first got my phone, within a week of owning it.
Points 1-3, exactly what happened mine.
Points 4 & 5 I didn't try, (was fairly new to Android)
Left it in to my local Vodafone shop & within 5 days I had it back in perfect working order, the maintenance report stated faulty hardware, the display module had to be replaced. Maybe worth mentioning to the service guy?

R34L2Pac said:
@frostygenius
I don´t think that your instrunctions ARE accuarate. You don´t even mention that he has to be in Download mode if he wants to use Odin. Also you advise to connect phone right after opening Odin and than insert the files, but some versions of Odin are known that they malfunctioning if you do this in this order, You should first insert files and set odin and after that plug in your phone.
And if he claims that he is on stock since bought the phone, so maybe he never used it before.
@peterg123
I´m not exactly following what happens to your phone. If I understand correctly the Samsung released defective ROM via KIES and after a week turn it down? But you already updated and now your phone is broken? If yes, I think that Samsung service center should repair your phone or if its serious damage than even replace it.
Is the phone able to boot-up and work properly? Is your recovery mode and/or download mode working? If the download mode (use 3-button combo - VolDown+Home+Power) is working then you can try recover on your own, but be careful, dont do anything before you are sure that you know what you are doing. You can go through this post before start [HOWTO] [REF] [FAQ] [Guides] [Tutorials] Flash/Root/ADB/ROM [MUST READ!].
Also go through the forum or samfirmware.com and find your official version of rom (Eclair 2.1) to be sure that you can anytime revert to this one because of warranty.
EDIT: Also can you please post some photos or video showing what happens to your phone?
Click to expand...
Click to collapse
Thanks for the heads-up I forgot to mention those points. I've updated my original post.
Sent from my GT-I9000 using Tapatalk

Thanks, it is not possible to get into download mode, or I would have done all that. As explained, the phone will not go past the giant "S" logo ( 3rd screen after power on). This problem has happened to many people, worldwide.
As explained the three button default firmware does not work.
The Samsung repair agent claims to have used the 301k resistor method to restart the phone and even that failed. I am not sure if this is true but he said so.. not sure because everybody reports success with this.
ODIN, as I said ( 1.8) recognises the COM connection just as does KIES. The problem is, I am not in download mode so can't reflash if I tried.
I have used the phone for 10 weeks since firmware upgrade from 2.1 to 2.2 during which I had no problems except the occasional process stopped errors.
Hope this help, thanks for trying for me

Yes you are correct, I can't get download mode. The phone has never been reflashed or messed with. It came with 2.1 and using KIES in March I reflashed to 2.2 and it worked perfectly for 10 weeks until it semi-bricked.
There is the Black Screen of eath...then there is the pulsasing S screen of limbo! That's what I have.
The only harwdare clue I have is the SGS blew the fuse in my car charger shortly before "expiring"...yet if connected to USB or other charger, it charges the battery and displays the logo.

peterg123 said:
Thanks, it is not possible to get into download mode, or I would have done all that. As explained, the phone will not go past the giant "S" logo ( 3rd screen after power on). This problem has happened to many people, worldwide.
As explained the three button default firmware does not work.
The Samsung repair agent claims to have used the 301k resistor method to restart the phone and even that failed. I am not sure if this is true but he said so.. not sure because everybody reports success with this.
ODIN, as I said ( 1.8) recognises the COM connection just as does KIES. The problem is, I am not in download mode so can't reflash if I tried.
I have used the phone for 10 weeks since firmware upgrade from 2.1 to 2.2 during which I had no problems except the occasional process stopped errors.
Hope this help, thanks for trying for me
Click to expand...
Click to collapse
..But download mode doesn't display the S logo or even the first Galaxy S 1900 logo...it goes straight in.
Try looking up in the Development section - I'm sure there is a jig method in there and it might be worth trying yourself, you've not got mush to lose now.
If you can get into download mode eventually, search for and flash Ezbase, that will get you onto a rooted firmware and it works EVERY single time for me. Good luck.

@R34L2Pac
Hi, thanks. As posted, the stock UK model SGS 1900 with 2.1 Eclair worked perfect from Nov to March 2011, was firmware upodated by KIES in March 2011 to 2.2.1 Froyo and worked like a dream until it went "semi-bricked" with the "Logo of Limbo" screen ( the pulsating giant S) for no reason.
A week before this, I changed SIMs when I changed countries and for some reason lost all added apps. I had to re-install them and even then, sometimes twice as I got many "android process stopped" errors --- even on some of the Sansung installed ones like Layar. That is the only problem I ever had.
The phone has only had apps from Market and never been modded whatsoever. Many thanks

Hi,
You said that you can see a pulsating S logo, sound to me like your phone is bootlooping. But you didnt mention if you can get at least to recovery(VolUp+Home+Power)? If you can get into recovery, you could try just factory reset your phone from recovery and reboot your system.
Also in the development forum you can find some kernels which can be flashed via recovery (like speedmod K13 for Froyo), so you can try to flash this kernel and after reboot into CWM recovery you could try to connect phone to ADB and type the command "adb reboot download".
I read on the forum that the home-made jig method worked for everyone, so looks like the samsung technician was doing something wrong. It is worth trying to made one a see what it does. Also found this thread, where user cuperus claims that even with charger can be simulated the jig by heating-up your device. So you can also try it, just plug your phone to a charger, let it charge for 1hour and than try use 3-button combo to go to download mode.

R34L2Pac said:
Hi,
You said that you can see a pulsating S logo, sound to me like your phone is bootlooping. But you didnt mention if you can get at least to recovery(VolUp+Home+Power)? If you can get into recovery, you could try just factory reset your phone from recovery and reboot your system.
Also in the development forum you can find some kernels which can be flashed via recovery (like speedmod K13 for Froyo), so you can try to flash this kernel and after reboot into CWM recovery you could try to connect phone to ADB and type the command "adb reboot download".
I read on the forum that the home-made jig method worked for everyone, so looks like the samsung technician was doing something wrong. It is worth trying to made one a see what it does. Also found this thread, where user cuperus claims that even with charger can be simulated the jig by heating-up your device. So you can also try it, just plug your phone to a charger, let it charge for 1hour and than try use 3-button combo to go to download mode.
Click to expand...
Click to collapse
Sorry I should have mentioned that it will not get into 3 button recovery mode, that has zero effect or rather, just sends it to the "Logo of Limbo" ( pulsating "S") just as does the power button.
Will maybe try a long charge time and see if that helps! Many thanks

Try en carefully learn hw to use odin coz I gt tha same exact model. I hav flashed mine many tyms en am on 2.3.4 XXJVP. if u do gt into download mode odin will sort u. Regards frm K.poly.
Sent from my GT-I9000 using XDA Premium App

peterg123 said:
Sorry I should have mentioned that it will not get into 3 button recovery mode, that has zero effect or rather, just sends it to the "Logo of Limbo" ( pulsating "S") just as does the power button.
Will maybe try a long charge time and see if that helps! Many thanks
Click to expand...
Click to collapse
how long have you tried holding down the 'volume down+menu+power' keys? a simple quick press of the three buttons does not work. you have to keep holding them all down for a bit (sometimes upto to 15-20 seconds) for it to go into download mode.

Sorry for the fast answer but I'm at work atm... I think he needs to do the 3 combo button fix on his phone first. I know it's on the forum somewhere... Can anyone check it for him? I lost the 3 combo the first time I updated with Keys from 2.1 to 2.2 and I had to fix it using a program that I can't remember to go on download mode and apply that fix.
Then he can use Odin to flash a stock rom as he needs, plus having 3 combo fixed!
Good luck mate!
Sent from my GT-I9000 using XDA App

Possible fix for your problem
Hi peterg,
I was looking through the general forum and found this post, where user beamzuk1 describes method how he fixed his semibricked phone. Symptoms are the same (not booting, glowing soft-keys, vibrating, no recovery and no download mode). So he used 'adb reboot recovery', I would say that proper command is 'adb reboot download', but you can try both. Also go through guide HOWTO use ADB, which I posted here the link in earlier post.
Hope this will help.
PS: Try follow beamzuk1 step-by-step, because if you start phone earlier than you connect it to pc, adb might not recognize the phone. Also be sure that you have correctly installed drivers and android-sdk before you try this.

These phones come with a 2 year warranty. Why don't you contact Samsung directly yourself - telling them that the local repair centre wouldn't fix/replace it for you. If you did nothing besides what you described, then I would have thought you were entitled to have it fixed or replaced by Samsung.

LiverpoolFCfan said:
These phones come with a 2 year warranty. Why don't you contact Samsung directly yourself - telling them that the local repair centre wouldn't fix/replace it for you. If you did nothing besides what you described, then I would have thought you were entitled to have it fixed or replaced by Samsung.
Click to expand...
Click to collapse
+1
Also think that Samsung should repair it or replace it.

The fact your repair center has done nothing to fix your phone, in several occasions, now entitles you to brand new replacement or your money refunded in full, contract terminated and expenses paid for your losses incurred as a result of their negligence.
Why not hit them up for the SGS 2.

I had the same issue with my first Galaxy S...wifi stopped working at first, I turned it off then on again but nothing changed. So I rebooted to see if it would correct itself. Bootloops and no 3 button combo (download or recovery)
Sent it off to Samsung through the Carphone Warehouse in the UK. I'd contact a Samsung Service Centre directly if I were you.

Amazon Blu R1 HD [Firmware] [Restore] [Unbrick] [Unroot]

How to Firmware Restore the Amazon Blu R1 HD
With the Help of many of you at XDA we have put together a working scatter file and I have pulled the Firmware from the device so that we can now restore this phone.
View attachment 3826922
STEPS TO RESTORE DEVICE AND BE ABLE TO HAVE ADS AND OTA UPDATES WORKING AGAIN
1. Download SP_Flash_Tool_BLU_R0010UU_V6.4_Firmware.zip
2. Extract the SP_Flash_Tool_BLU_R0010UU_V6.4_Firmware.zip to your desktop. Note 7zip is great to extract files.
3. lauch Flash_tool.exe
4. select scatter-loading and browser to load MT6735_Android_scatter_R1_HD_Amazon.txt
5. click download button to start.
6. now plug your phone into the computer. to boot the device to preloader and start the flash. You can do it two ways: 1. power off the phone and flash will start or 2. From a powered off stat power on the device while plugged into the computer. either way will start the sp flash tool.
7. once the flash is complete you can unplug the device and reboot it with the power button. Congrats you have fully restored your Amazon Blu R1 HD. Bonus you have also enabled bootloader unlocking if you want it.
Tutorial Video with all the steps need to restore.
NOTE: This has been fully tested on the Amazon R1 HD 16GB model but should work on the 8gb also.

You're the man!

Hi, I keep getting this error:
BROM ERROR: S_DL_GET_DRAM_SETTING_FAIL(0x13BE)
[EMI]Obtain DRAM Failed!
[HINT]:
Please check your load matches to your target which is to be downloaded
Do you have any idea how to fix it? Thanks.

Dude this doesnt work for me.
When I plug in my phone, a popup from Flash tools comes up saying, "PMT changed for the ROM; it must be downloaded."
Then what?

johnsmithsir12 said:
Dude this doesnt work for me.
When I plug in my phone, a popup from Flash tools comes up saying, "PMT changed for the ROM; it must be downloaded."
Then what?
Click to expand...
Click to collapse
EDIT - DO NOT USE THE DOWNLOAD+FORMAT MODE EVER ON THE R1, IT WILL RESULT IN A BRICK, IT MAY WORK ON OTHER MTK MODELS, BUT EXPERIENCE HAS SHOWN IT WILL BRICK THE R1 HD!!!! DOWNLOAD ONLY IS THE ONLY SAFE METHOD!!
Occurs if the names or addresses of the blocks in the scatter differ from the table inside the phone (PMT).
Thats not good, i suggest maybe checking the scatter file making sure its not currupt... Or try the following alternate solution....
http://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
This also seems to be a solution,but perhaps more dangerous last ditch effort maybe?? The video is for a different MTK SoC, but from what what im reading it's the same technique across the MTK lineup..
Perform at your own discretion, not responsible for bricked devices....

kal250 said:
Occurs if the names or addresses of the blocks in the scatter differ from the table inside the phone (PMT).
Thats not good, i suggest maybe checking the scatter file making sure its not currupt... Or try the following alternate solution....
http://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
This also seems to be a solution,but perhaps more dangerous last ditch effort maybe?? The video is for a different MTK SoC, but from what what im reading it's the same technique across the MTK lineup..
Perform at your own discretion, not responsible for bricked devices....
Click to expand...
Click to collapse
I rooted my phone via this method: http://forum.xda-developers.com/r1-hd/how-to/twrp-how-to-root-t3425677
Keep in mind, only "recovery" was checked and nothing else.

yujiba said:
Hi, I keep getting this error:
BROM ERROR: S_DL_GET_DRAM_SETTING_FAIL(0x13BE)
[EMI]Obtain DRAM Failed!
[HINT]:
Please check your load matches to your target which is to be downloaded
Do you have any idea how to fix it? Thanks.
Click to expand...
Click to collapse
Try this: http://onlinejobwithoutanyinvestment.com/sp-flash-tool-errors-fix-brom-error/
Format your phone, but not the bootloader, and then try reflashing

We're seeing reports of this bricking phones. If you are considering trying it, don't! If you have bricked your phone, please join our Hangout right here and cooperate with us to find the cause of the brick and a way to unbrick it!
Join the conversation on Hangouts: https://hangouts.google.com/group/Q5wGs6508l1rqGng2
Sent from my LG G4 using XDA Labs

ColtonDRG said:
We're seeing reports of this bricking phones. If you are considering trying it, don't! If you have bricked your phone, please join our Hangout right here and cooperate with us to find the cause of the brick and a way to unbrick it!
Join the conversation on Hangouts: https://hangouts.google.com/group/Q5wGs6508l1rqGng2
Click to expand...
Click to collapse
The format method, i stumbled upon, i just added as a last ditch effort, I'm not sure whats causing the errors to begin with. The scatter addresses all still match the block addresses mapped in the new OTA, so that theory is shot, im not sure what else could be going on.

If SPFT WON'T FLASH
1. Power off your phone.
2. Hold the power and volume up buttons then choose "recovery" from the menu that shows up.
(volume buttons = up/down, power button = ok/select)
3. Now choose power off.
Doing the above makes sure your phone is COMPLETELY shut off, windows can find your phone, and SPFT will be able to flash it.
I believe that, when you use "power off", from within android, it actually puts the phone in some type of suspend or hibernation mode. I say this because you can hit the power button and it will boot very quickly after powering off within android, but from recovery it takes longer to boot. This was the case with mine.
Your only other option is to let the battery completely drain, then try SPFT.
SHOUT OUT TO ALL THE GUYS THAT ROOTED THIS SUCKER AND UNLOCKED IT! GREAT WORK! ???? :good:

burnanator said:
If SPFT WON'T FLASH
1. Power off your phone.
2. Hold the power and volume up buttons then choose "recovery" from the menu that shows up.
(volume buttons = up/down, power button = ok/select)
3. Now choose power off.
Doing the above makes sure your phone is COMPLETELY shut off, windows can find your phone, and SPFT will be able to flash it.
I believe that, when you use "power off", from within android, it actually puts the phone in some type of suspend or hibernation mode. I say this because you can hit the power button and it will boot very quickly after powering off within android, but from recovery it takes longer to boot. This was the case with mine.
Your only other option is to let the battery completely drain, then try SPFT.
SHOUT OUT TO ALL THE GUYS THAT ROOTED THIS SUCKER AND UNLOCKED IT! GREAT WORK! ???? :good:
Click to expand...
Click to collapse
Never occurred to try that, curse this trend of non removable batteries anyways -_-

kal250 said:
Never occurred to try that, curse this trend of non removable batteries anyways -_-
Click to expand...
Click to collapse
Yup. That's why i tried it. This is the first phone i have had with a non-removable battery.

johnsmithsir12 said:
Dude this doesnt work for me.
When I plug in my phone, a popup from Flash tools comes up saying, "PMT changed for the ROM; it must be downloaded."
Then what?
Click to expand...
Click to collapse
I just saw your other thread you started
http://forum.xda-developers.com/r1-hd/how-to/question-restoring-to-factory-default-t3440059
And now I see why you had this error. You have the 8gb version not the 16gb. So this method uses the wrong scatter file for you phone. Please update the forum if you still have the phone and need assistance. There are some commands that you can run in adb to see the partition sizes and then with that the scatter file can be adjusted for your phone

sorry for being off topic here but i really need to know if its possible to unlock more 4g bands , in my contry they don't release the infomation of what bands the providers work so its a guessing game, since i got this phone i purchased the 4g sim card , even with the band 12 update still stuck at 3g , even with proper 4g apn still stuck at 3g wich i came to a conclusion that the 4g bands from the Blu R1 HD are not the same as my providers...in conclusion can it be done ( open up more bands to see wich band will get me the 4g) and if so please explain to me how i can do so please.

This worked for me, but I had to factory reset after because OTA was still detecting root.

Help me!
hello, I do all the steps but remains in the logo and reboots

THIS DOES NOT WORK WITH 8GB/1GB version :'(

Hello,
I just want to unroot my Blu R1, what should I do?

DOA Bricked
Any hope for an R1 which will now not even power up?

This will not work on any of the latest versions. My model is a 2GB/16GB - I was on Coltons root and tried this to go back to stock with my phone now stuck in boot loop.
Do not use this method.

Lenovo Tab 3 8 (TB3-850M) - Hard Bricked

Hi,
It looks my tablet got hardbricked. Apparently, it looks like it was turned off completely automatically, when in sleep mode. When it's powered off now - pressing power button for a while makes nothing. When connected to charger - white LED flash is blinking only and when trying to power on, and there is no "Lenovo" logo at all. I've tried some of "power cycle" tutorials - but no luck. Once, when using power button, tablet was vibrating crazily and screen blinked, but it was shut down after moment.
Sorry, if there is existing similar thread - this tablet is not very popular. If there is any "magic trick" to make it work, I'll be grateful, if now - probably I'll need to flash new firmware. Currently, I'm discharging it completely.
Best regards.

wxtester said:
Hi,
It looks my tablet got hardbricked. Apparently, it looks like it was turned off completely automatically, when in sleep mode. When it's powered off now - pressing power button for a while makes nothing. When connected to charger - white LED flash is blinking only and when trying to power on, and there is no "Lenovo" logo at all. I've tried some of "power cycle" tutorials - but no luck. Once, when using power button, tablet was vibrating crazily and screen blinked, but it was shut down after moment.
Sorry, if there is existing similar thread - this tablet is not very popular. If there is any "magic trick" to make it work, I'll be grateful, if now - probably I'll need to flash new firmware. Currently, I'm discharging it completely.
Best regards.
Click to expand...
Click to collapse
Are you still bricked? There is the firmware flashing method using SP Flash Tool which restores both the 850F & 850M to full factory condition. Let me know if you need the method and I'll get you links to the guides here on XDA.

AeonFlux1603 said:
Are you still bricked? There is the firmware flashing method using SP Flash Tool which restores both the 850F & 850M to full factory condition. Let me know if you need the method and I'll get you links to the guides here on XDA.
Click to expand...
Click to collapse
Yes. I've asked for help guy from unauthorized repair service, he said device is completely bricked, probably EEPROM chip is broken. But ok, you can send me this instruction of course

wxtester said:
Yes. I've asked for help guy from unauthorized repair service, he said device is completely bricked, probably EEPROM chip is broken. But ok, you can send me this instruction of course
Click to expand...
Click to collapse
I've had two 850F devices hard bricked and was able to recover using SP Flash Tool and a stock firmware package. I'll get you the method posted here. But, out of curiosity, how did you hard brick yours?
(The 850F is pretty much an 850M without SIM/data connectivity support. They also have slightly different chipsets, but many of the specs are very similar. So, I know the method will work on both variants of the Tab3 8.

AeonFlux1603 said:
I've had two 850F devices hard bricked and was able to recover using SP Flash Tool and a stock firmware package. I'll get you the method posted here. But, out of curiosity, how did you hard brick yours?
(The 850F is pretty much an 850M without SIM/data connectivity support. They also have slightly different chipsets, but many of the specs are very similar. So, I know the method will work on both variants of the Tab3 8.
Click to expand...
Click to collapse
Hey, thanks for you reply! As I'm not owner of the tablet, it's hard to say how it was bricked. It was on stock firmware, it was not rooted and TWRP was not installed. I've helped to configure this tablet, tablet was turned off everyday at 11PM automatically, and powered on manually, by device owner. She said sometimes instead of powering on to Android, it was booting into FASTBOOT mode (green android image). Once, it just failed to boot, without any reaction. I've tried to recover it using Windows machine, when plugging it into computer (no matter, with, or without Vol+ pressed) it was recognized as Unknown device (instead of Qualcomm, or something). I've tried many drivers - but with no luck, device was not recognized. Also, I've tried 2 machines with Win7 & Windows XP. I've managed to reboot device using power key long pressed, but starting from this point device was not recognized at all... When plugged into USB, nothing was happening. Service guy said he was able to make his computer recognize device using some technical cable plugged directly with motherboard, but all methods to flash firmware failed. He said probably EEPROM chip is broken completely and replacing this part is half of device cost. Thing is, this tablet was bought from China - so no guarantee at all. Well, probably she need to buy next tablet from local electronic store...

wxtester said:
Hey, thanks for you reply! As I'm not owner of the tablet, it's hard to say how it was bricked. It was on stock firmware, it was not rooted and TWRP was not installed. I've helped to configure this tablet, tablet was turned off everyday at 11PM automatically, and powered on manually, by device owner. She said sometimes instead of powering on to Android, it was booting into FASTBOOT mode (green android image). Once, it just failed to boot, without any reaction. I've tried to recover it using Windows machine, when plugging it into computer (no matter, with, or without Vol+ pressed) it was recognized as Unknown device (instead of Qualcomm, or something). I've tried many drivers - but with no luck, device was not recognized. Also, I've tried 2 machines with Win7 & Windows XP. I've managed to reboot device using power key long pressed, but starting from this point device was not recognized at all... When plugged into USB, nothing was happening. Service guy said he was able to make his computer recognize device using some technical cable plugged directly with motherboard, but all methods to flash firmware failed. He said probably EEPROM chip is broken completely and replacing this part is half of device cost. Thing is, this tablet was bought from China - so no guarantee at all. Well, probably she need to buy next tablet from local electronic store...
Click to expand...
Click to collapse
Yeah, the service guy is full of it without any doubt. Using a modded fastboot cable, like he was likely referring to, will not only fail to push firmware to the eMMC, but will very likely damage or corrupt the partition index. I can't promise my method will work, but I can say with some certainty that it will. Ok, first things firstt: install the latest SP Flash Tool on your Windows PC or laptop. Also, you will need to install the latest vCOM drivers (for the Mediatek chipset). Do you know how to do this or do you need links? I can post a link for unbricking the 850F, which has been reported to work on 850M, but the thread is a bit erratic and non-concise. It will be much easier if you and I do this step by step. Also, you will need a stock firmware package for your 850M (build version is not relevant). Do you have one or do you need a link?
In a nutshell, this method will do an emergency recovery by directly pushing a stock firmware package to the device's eMMC flash memory. Although your PC is not currently recognizing your device, the vCOM drivers/SP Flash Tool, & your volume down button, will force recognition of the Mediatek chipset. Again, I cannot promise this will be successful, but I can say I've not yet seen a single hard bricked Tab 3 that could not be recovered from a hard brick this way.
Step 1 -- install the latest vCom drivers on your Windows (7, 8.1, or 10) PC/laptop. Here is an excellent XDA tutorial that provides sources and detailed instructions. https://forum-xda--developers-com.c...-10-mtk-vcom-usb-drivers-32-64-t3267033/page1 Sorry for the lengthy url.
Step 2 -- install the latest SP Flash Tool on your PC or laptop. Go to this website for download sources; https://spflashtool.com/
Step 3 -- download a stock firmware package for your TB3-850M. This is a link for a solid firmware package, confirmed to work (take note that build version isn't a factor. The SP Flash Tool will push a downgrade, upgrade, or collateral installation {same build version}): https://cloud.mail.ru/public/LHhe/NkpAi7WuL
When you've completed the above 3 steps, let me know and we will go forward with the firmware recovery process. :good:

I have the same issue. I dont know how but i got hard bricked completely. I was flashing rom on it and it got bricked. Now service centre guy is saying that i have to change motherboard altogether. But your post seems convincing. Please let me know the next detailed process.

i have the same issue.
one day stop working

AeonFlux1603 said:
Yeah, the service guy is full of it without any doubt. Using a modded fastboot cable, like he was likely referring to, will not only fail to push firmware to the eMMC, but will very likely damage or corrupt the partition index. I can't promise my method will work, but I can say with some certainty that it will. Ok, first things firstt: install the latest SP Flash Tool on your Windows PC or laptop. Also, you will need to install the latest vCOM drivers (for the Mediatek chipset). Do you know how to do this or do you need links? I can post a link for unbricking the 850F, which has been reported to work on 850M, but the thread is a bit erratic and non-concise. It will be much easier if you and I do this step by step. Also, you will need a stock firmware package for your 850M (build version is not relevant). Do you have one or do you need a link?
In a nutshell, this method will do an emergency recovery by directly pushing a stock firmware package to the device's eMMC flash memory. Although your PC is not currently recognizing your device, the vCOM drivers/SP Flash Tool, & your volume down button, will force recognition of the Mediatek chipset. Again, I cannot promise this will be successful, but I can say I've not yet seen a single hard bricked Tab 3 that could not be recovered from a hard brick this way.
Step 1 -- install the latest vCom drivers on your Windows (7, 8.1, or 10) PC/laptop. Here is an excellent XDA tutorial that provides sources and detailed instructions. https://forum-xda--developers-com.cdn.ampproject.org/v/s/forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033/amp/?amp_js_v=a2&amp_gsa=1&usqp=mq331AQCCAE=#aoh=15510379323239&amp_ct=1551037935701&referrer=https://www.google.com&amp_tf=From %1$s&ampshare=https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033/page1 Sorry for the lengthy url.
Step 2 -- install the latest SP Flash Tool on your PC or laptop. Go to this website for download sources; https://spflashtool.com/
Step 3 -- download a stock firmware package for your TB3-850M. This is a link for a solid firmware package, confirmed to work (take note that build version isn't a factor. The SP Flash Tool will push a downgrade, upgrade, or collateral installation {same build version}): https://cloud.mail.ru/public/LHhe/NkpAi7WuL
When you've completed the above 3 steps, let me know and we will go forward with the firmware recovery process. :good:
Click to expand...
Click to collapse
what is next? i have a tab 3 710f that is very dead.. hardbricked in wont boot into nothing.. black screen like its shut down

Lenovo Yoga 2 1050F Bricked

Hello,
A friend give to me his Yoga2 1050F Tab, because it's bricked...
"After a kind of upgrade he said"
So, here's the situation,
Tab is really bricked, stuck on Lenovo Android Screen.
I've tried to factory restore, no success.
I've searched all the web after factory image to flash, I've found 3 of them... But nothing works !!
The 1st one, the only we can still found here, is a factory image from 2015. And the result is, no more lenovo android screen, i'm stuck on a kind of Bios (?) And can't do anything more...
2nd one, (YT2-1050F_S100196_151123_ROW-fastboot), best result, back to an android boot, but stuck on recovery screen, without any possibility to boot...
3rd one (YT2-1050F_S0198_150422_ROW) impossible to flash, it's always failed at "flash easyimage.zip" step.
Other thing, I don't know what xml file I need to use (flash, flash-blankphone, flash-factory ... )
Here, i'm totally lost. Tab is stuck, And I've no idea what can I do next...
Maybe here anyone can help me ?
Many Many thanks !

Hello,
It seem's i got the same problem.
The tablet downloaded an upgrade by it's own.
The tablet rebooted alone and the try to apply the upgrade but never success.
Now i'm booting on a BIOS type screen.
"VALLEYVIEW C0 PLATFORM"
I can access to different options but the tablet is not reconized by my PC anymore.
I can flash anything on it.
If someone have a solution, it would be great !

Hey @NeedaVirus,
Sorry to hear that the device is bricked. Just this past weekend, I've been sifting through all my old resources because a recent OTA (Yep, a 2020 update!) left both me and my partner's 1050F devices in an unbootable state. You can see we're not alone by checking out the thread on the Lenovo forums (https://forums.lenovo.com/t5/Androi...Tablet-2-1050f-system-update-2020/m-p/5007166). Unfortunately a large number of the very helpful resources on xda seem to have been redacted/removed over the past few years, which leaves a few people scratching their heads (I was for a while too).
Basically, the way I've always done this on the 1050F (and what worked yesterday again), is as follows:
1. Install the "IntelAndroidDrvSetup1.10.0". Google will find this easy enough.
2. Install the flash tool. Nowadays, "Intel Platform Flash Tool Lite 5.8.4.0" (might also be called Phone Flash Tool Lite v5.8.4.0 and again google will find this for you) seems to come bundled with all required drivers, so it's a simple process to install.
3. Plug the device in and put it in DNX mode. This mode is achieved by holding vol up + vol down and pressing the power button until the device vibrates. When you feel the buzz, let go of power but hold the other two until you see a "Fastboot starting..." message on a black screen. This is DNX mode.
4. Restore stock KitKat bios using the "restore-kitkat-bios-830-1050-v2" tool. This one might take a little finding and I'm not sure if sharing it here is acceptable any more. Provided the device is plugged in and in DNX mode (and you have the Intel Platform Flash Tool closed too), it's just a matter of running the bios restore tool and following the prompts. Make sure the flash tool is running on your local drive (usually C).
5. Once the bios is pushed, we need to restore the stock KitKat ROM using the platform flash tool.
First we need to set up the Platform Flash Tool, so open that and select "File" -> "Options". Under "Flash options" tick the "Force fastboot sparsing" option and select "500MB" for the size.
6. Now, we want to use the "YT2-1050F_S0198_150422_ROW" image and you'll need to extract it first. It sounds like you already have the right archive file for this, which is good because I'm not sure if a copy still exists here still.
In the Platform Flash Tool, hit "Browse" and the file we're looking for is "target_bin\flash.xml". Select that. (Side note: I suspect that if your device has been updated to Lollipop in the past, you wouldn't have had any luck flashing this rom without rolling the bios back first).
7. Put the device into DNX mode again, and the Platform Flash Tool should see it (a "Baytrail" device is listed).
Now it's just a matter of starting the flash process by clicking the button.
8. Once the device is flashed, you'll need to reboot it (via the device) but wait for the flash process to report 100% first. Hitting the device power button is the way to confirm this reboot btw. It might take a few mins to get into Android here. This is normal.
9. Now, the device will boot into stock KitKat. We need to set the region though:
Open contacts, add new contact (only if you have none, we just need one).
Now, using the contact search, enter ####6020# and you'll be prompted to select your region. The device will reboot and you'll need to set a few things up again.
10. Run all the OTA updates to get right up to date. Just do this via android itself.
Optional: Do any other crazy bootloader unlocks, roots as desired. A lot of the original resources have been removed for these processes, but where there's a will, there's a way.
I'm sure there are other shortcuts to this process too. I think tontonfraguer was able to just flash a newer rom directly to resolve his bootloop, judging by his forum post over on the Lenovo thread. This is just the process I use, any feedback/improvements are most welcome!
Hopefully it helps someone being hit by the recent bootloops.
Cheers

OMG ! OMG ! OMG !!!
Man, you're THE MAN !!!
I've followed all your explanations, and... IT WORKS !!!
Yes it was hard to find again the "restore-kitkat-bios-830-1050-v2" (China links to Russian Servers...) But I've finded it !
Many many MAAAAANYYYY Thanks my friend !!!
Thanks a lot !
And thanks a lot to All XDA DEV !

dallivadr said:
Hey @NeedaVirus,
Sorry to hear that the device is bricked. Just this past weekend, I've been sifting through all my old resources because a recent OTA (Yep, a 2020 update!) left both me and my partner's 1050F devices in an unbootable state. You can see we're not alone by checking out the thread on the Lenovo forums (https://forums.lenovo.com/t5/Androi...Tablet-2-1050f-system-update-2020/m-p/5007166). Unfortunately a large number of the very helpful resources on xda seem to have been redacted/removed over the past few years, which leaves a few people scratching their heads (I was for a while too).
Basically, the way I've always done this on the 1050F (and what worked yesterday again), is as follows:
1. Install the "IntelAndroidDrvSetup1.10.0". Google will find this easy enough.
2. Install the flash tool. Nowadays, "Intel Platform Flash Tool Lite 5.8.4.0" (might also be called Phone Flash Tool Lite v5.8.4.0 and again google will find this for you) seems to come bundled with all required drivers, so it's a simple process to install.
3. Plug the device in and put it in DNX mode. This mode is achieved by holding vol up + vol down and pressing the power button until the device vibrates. When you feel the buzz, let go of power but hold the other two until you see a "Fastboot starting..." message on a black screen. This is DNX mode.
4. Restore stock KitKat bios using the "restore-kitkat-bios-830-1050-v2" tool. This one might take a little finding and I'm not sure if sharing it here is acceptable any more. Provided the device is plugged in and in DNX mode (and you have the Intel Platform Flash Tool closed too), it's just a matter of running the bios restore tool and following the prompts.
5. Once the bios is pushed, we need to restore the stock KitKat ROM using the platform flash tool.
First we need to set up the Platform Flash Tool, so open that and select "File" -> "Options". Under "Flash options" tick the "Force fastboot sparsing" option and select "500MB" for the size.
6. Now, we want to use the "YT2-1050F_S0198_150422_ROW" image and you'll need to extract it first. It sounds like you already have the right archive file for this, which is good because I'm not sure if a copy still exists here still.
In the Platform Flash Tool, hit "Browse" and the file we're looking for is "target_bin\flash.xml". Select that. (Side note: I suspect that if your device has been updated to Lollipop in the past, you wouldn't have had any luck flashing this rom without rolling the bios back first).
7. Put the device into DNX mode again, and the Platform Flash Tool should see it (a "Baytrail" device is listed).
Now it's just a matter of starting the flash process by clicking the button.
8. Once the device is flashed, you'll need to reboot it (via the device) but wait for the flash process to report 100% first. Hitting the device power button is the way to confirm this reboot btw. It might take a few mins to get into Android here. This is normal.
9. Now, the device will boot into stock KitKat. We need to set the region though:
Open contacts, add new contact (only if you have none, we just need one).
Now, using the contact search, enter ####6020# and you'll be prompted to select your region. The device will reboot and you'll need to set a few things up again.
10. Run all the OTA updates to get right up to date. Just do this via android itself.
Optional: Do any other crazy bootloader unlocks, roots as desired. A lot of the original resources have been removed for these processes, but where there's a will, there's a way.
I'm sure there are other shortcuts to this process too. I think tontonfraguer was able to just flash a newer rom directly to resolve his bootloop, judging by his forum post over on the Lenovo thread. This is just the process I use, any feedback/improvements are most welcome!
Hopefully it helps someone being hit by the recent bootloops.
Cheers
Click to expand...
Click to collapse
Cant find anywhere to download restore-kitkat-bios-830-1050-v2 file. Any chance you could pm a Google drive link?
Thanks

Sansiro2 said:
Cant find anywhere to download restore-kitkat-bios-830-1050-v2 file. Any chance you could pm a Google drive link?
Thanks
Click to expand...
Click to collapse
Managed to sort it out - many thanks for your guide. One thing to note is the Kitkit restore file needs to be in the root of the C drive and also the file for the flash in my case was the flash.xml file

Glad the post helped you guys out and that you were able to get back up and running. If the post was helpful, why not click the 'thank' button under my post

Hi Hi Hiiii
For those who need the famous "restore-kitkat-bios-830-1050-v2"
HERE'S THE LINK (Personal re-upload) : https://drive.google.com/file/d/13vV6fpNAbWWZUk9_fzmJpMAMax2tlyyB/view?usp=sharing
Be aware that you probably need to do this if your OTA updates Fails :
If system update fails do the following:
1. Flash stock firmware
2. Optionally you can wipe user data (I never did that) from DROIDBOOT
3. Go to contacts manager. Create some dummy contact if list is empty.
4. Go to Search / Find Contacts and enter ####6020#. It will ask you to select country code (first two latin letters, ignore Chinese).
5. Select what you want, then reboot.
6. Go to System Update
7. Install OTA update
(Original Post here : https://forum.xda-developers.com/showpost.php?p=57846051&postcount=233)
Enjoy Friends

NeedaVirus said:
Hi Hi Hiiii
For those who need the famous "restore-kitkat-bios-830-1050-v2"
HERE'S THE LINK (Personal re-upload) : https://drive.google.com/file/d/13vV6fpNAbWWZUk9_fzmJpMAMax2tlyyB/view?usp=sharing
Be aware that you probably need to do this if your OTA updates Fails :
If system update fails do the following:
1. Flash stock firmware
2. Optionally you can wipe user data (I never did that) from DROIDBOOT
3. Go to contacts manager. Create some dummy contact if list is empty.
4. Go to Search / Find Contacts and enter ####6020#. It will ask you to select country code (first two latin letters, ignore Chinese).
5. Select what you want, then reboot.
6. Go to System Update
7. Install OTA update
(Original Post here : https://forum.xda-developers.com/showpost.php?p=57846051&postcount=233)
Enjoy Friends
Click to expand...
Click to collapse
Thanks - when setting the country code if you get the 'ERROR : could not read factory ota patch from sd card,or the patch is not correct.' then you need to take the easyimage.zip from the extracted rom folder and copy it on the sdcard (on the root of it not in some folder) then try again (with at least 30% battery level).

Guys,
If someone wants to ROOT his tablet, I can write the procedure. (Many try for me before it really works...)
See ya !

hi everyone , i hope someone be able to help me with this , i also just got this tablet as one that does not even turn on , ive played with it a bit and managed to get some writings on the display, then i found this topic here and tried to follow as instructed, nothing happens, and the screen with fastboot starting goes off. any suggestion ?
thank you in advance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

THANK YOU!!
i have been battling with the TY2 1380f for a whole week with just a black screen. This helped as I was able to find the kit kat restore for the 1380 and following your guide, got things back to normal.
Life Saver!!!
dallivadr said:
Hey @NeedaVirus,
Sorry to hear that the device is bricked. Just this past weekend, I've been sifting through all my old resources because a recent OTA (Yep, a 2020 update!) left both me and my partner's 1050F devices in an unbootable state. You can see we're not alone by checking out the thread on the Lenovo forums (https://forums.lenovo.com/t5/Androi...Tablet-2-1050f-system-update-2020/m-p/5007166). Unfortunately a large number of the very helpful resources on xda seem to have been redacted/removed over the past few years, which leaves a few people scratching their heads (I was for a while too).
Basically, the way I've always done this on the 1050F (and what worked yesterday again), is as follows:
1. Install the "IntelAndroidDrvSetup1.10.0". Google will find this easy enough.
2. Install the flash tool. Nowadays, "Intel Platform Flash Tool Lite 5.8.4.0" (might also be called Phone Flash Tool Lite v5.8.4.0 and again google will find this for you) seems to come bundled with all required drivers, so it's a simple process to install.
3. Plug the device in and put it in DNX mode. This mode is achieved by holding vol up + vol down and pressing the power button until the device vibrates. When you feel the buzz, let go of power but hold the other two until you see a "Fastboot starting..." message on a black screen. This is DNX mode.
4. Restore stock KitKat bios using the "restore-kitkat-bios-830-1050-v2" tool. This one might take a little finding and I'm not sure if sharing it here is acceptable any more. Provided the device is plugged in and in DNX mode (and you have the Intel Platform Flash Tool closed too), it's just a matter of running the bios restore tool and following the prompts. Make sure the flash tool is running on your local drive (usually C).
5. Once the bios is pushed, we need to restore the stock KitKat ROM using the platform flash tool.
First we need to set up the Platform Flash Tool, so open that and select "File" -> "Options". Under "Flash options" tick the "Force fastboot sparsing" option and select "500MB" for the size.
6. Now, we want to use the "YT2-1050F_S0198_150422_ROW" image and you'll need to extract it first. It sounds like you already have the right archive file for this, which is good because I'm not sure if a copy still exists here still.
In the Platform Flash Tool, hit "Browse" and the file we're looking for is "target_bin\flash.xml". Select that. (Side note: I suspect that if your device has been updated to Lollipop in the past, you wouldn't have had any luck flashing this rom without rolling the bios back first).
7. Put the device into DNX mode again, and the Platform Flash Tool should see it (a "Baytrail" device is listed).
Now it's just a matter of starting the flash process by clicking the button.
8. Once the device is flashed, you'll need to reboot it (via the device) but wait for the flash process to report 100% first. Hitting the device power button is the way to confirm this reboot btw. It might take a few mins to get into Android here. This is normal.
9. Now, the device will boot into stock KitKat. We need to set the region though:
Open contacts, add new contact (only if you have none, we just need one).
Now, using the contact search, enter ####6020# and you'll be prompted to select your region. The device will reboot and you'll need to set a few things up again.
10. Run all the OTA updates to get right up to date. Just do this via android itself.
Optional: Do any other crazy bootloader unlocks, roots as desired. A lot of the original resources have been removed for these processes, but where there's a will, there's a way.
I'm sure there are other shortcuts to this process too. I think tontonfraguer was able to just flash a newer rom directly to resolve his bootloop, judging by his forum post over on the Lenovo thread. This is just the process I use, any feedback/improvements are most welcome!
Hopefully it helps someone being hit by the recent bootloops.
Cheers
Click to expand...
Click to collapse

hello

hoooman008 said:
hi everyone , i hope someone be able to help me with this , i also just got this tablet as one that does not even turn on , ive played with it a bit and managed to get some writings on the display, then i found this topic here and tried to follow as instructed, nothing happens, and the screen with fastboot starting goes off. any suggestion ?
thank you in advance.View attachment 5176433View attachment 5176431
Click to expand...
Click to collapse
any help would be greatly appreciated

hoooman008 said:
any help would be greatly appreciated
Click to expand...
Click to collapse
on your screen, attached, at device manager, i can see the driver for intel adb fastboot blabla is not correctly installed, try:
1. restarting windows while holding SHIFT button till it restarts
2. go through advanced restart option and select startup settings
3. when it reboots and offers to select in black-white options 1-8, select wit button F7 the "driver signature.." part
( you are now allowing to installing unsigned drivers )
4. wehn it reboots, INSTALL intel plattform flash tool.exe again and re-install everyting, this time u will see windows pop-ups in red notifiying you installing unsigned extra extra drama drivers, say yes to all of them
5. flash again, using above instructions, make sure to change intel plattform flash tool settings to force flash 500MB
6. go everyting that is instructed above - step by step - through and report, i had exact same problem and solved it remembering the driver-stuffs weirdness on windows, still not a problem at all, just anoying extra steps

NeedaVirus said:
Hello,
A friend give to me his Yoga2 1050F Tab, because it's bricked...
"After a kind of upgrade he said"
So, here's the situation,
Tab is really bricked, stuck on Lenovo Android Screen.
I've tried to factory restore, no success.
I've searched all the web after factory image to flash, I've found 3 of them... But nothing works !!
The 1st one, the only we can still found here, is a factory image from 2015. And the result is, no more lenovo android screen, i'm stuck on a kind of Bios (?) And can't do anything more...
2nd one, (YT2-1050F_S100196_151123_ROW-fastboot), best result, back to an android boot, but stuck on recovery screen, without any possibility to boot...
3rd one (YT2-1050F_S0198_150422_ROW) impossible to flash, it's always failed at "flash easyimage.zip" step.
Other thing, I don't know what xml file I need to use (flash, flash-blankphone, flash-factory ... )
Here, i'm totally lost. Tab is stuck, And I've no idea what can I do next...
Maybe here anyone can help me ?
Many Many thanks !
Click to expand...
Click to collapse
Download Lenovo's official "Rescue and Smart Assistant" it reflashes stock rom for you.

Samsung S10 + bootloop ERASE FAIL: READ ONLY

Samsung S10 + SM-F975F/DS IMEI stating Taiwan (Update: Very contradicting information if the phone is Snapdragon OR Exynos) if it even matters to solve the issue I dont know
Owner of the above since 2019 without issues; USB debugging mode activated in 2019 and never changed since then.
Samsung always updated which I assume the UI 3 Android got updated in January of my vague memory/recollection (honestly never paid attention of what is being updated, only that the phone needs to be on charge while doing ANY update)
Issue: phone in constant bootloop every 4 minutes with top message in red color "ERASE FAIL: READ ONLY" see photo attached
Cause: happened 4 days ago: Watched video stream on chrome browser; phone froze and applied a 10sec. power shut off (never had to do that before, 1st time)
Investigation:
I tried (found out by doing so) to interrupt the bootloop with pressing Power button and same time Volume Down Button in order to restart it and follow the following commands found on the internet as per UI 3 update:
Recovery Mode as followed does nothing:
Hold the Power button of your device till the power menu pops up and select Power Off. = does not apply as in bootloop
Wait for your device to turn off completely. = it does never turn off completely UNLESS I press Power button and same time Volume Down Button und plug into USB C Data cable of which the charging circle with the lightening strike appears without any percentage % of which photo is attached (phone charge can keep up with its bootloop in order to avoid battery drainage as there is no % indication)
Plug-in a USB-C data cable connected to your PC or USB-C earphones in your device. = I start from here whenever the phone restarts every 4 minutes or whenever I do it manually by pressing the buttons as I described in point 2.
Now, check if your device has a Bixby Button (Such as Galaxy S10/Note10):
Without Bixby Button: Press Volume Up + Power Button for a few seconds.
With Bixby Button: Press Volume Up + Bixby Button + Power Button for a few seconds
After the above steps, you will boot into Recovery mode.
Download Mode as followed does nothing: IT DOES WORK NOW you need to be very fast before the phone starts (recovery mode does not work)
Make sure you have a USB cable connected to the computer
Then press and hold the Volume Down and Bixby buttons at the same time
Continue holding these two buttons down while you insert the USB cable that is connected to the PC
Recovery Mode before update instructions as followed does nothing:
Step 1: Start by turning off your Galaxy S10.
Step 2: After it’s powered down, press and hold Volume Up button and Bixby button (this is the button underneath the volume buttons in case you didn’t know).
Step 3: Without letting go of the Volume Up and Bixby buttons, press and hold the Power button.
Step 4: As soon as your device turns on, let go of the Power button.
Step 5: After you see a blue screen, let go of the remaining two buttons. Now you are in Recovery mode.
Download Mode before update instructions as followed does nothing:
Step 1: Turn off your Galaxy S10.
Step 2: When it’s turned off, press and hold the Volume Down button and Bixby button.
Step 3: Without letting go of the two buttons, press and hold the Power button.
Step 4: You will get into Download Mode.
Have tried all the above methods several times the past 4 days.
Have drained the battery in terms of keeping the phone in bootloop resulting in no power.
Unhooked the battery by means of removing the rear panel and unhooking the battery cable for more then 15minutes and repeat the 4 different methods
Unhooked the mainboard from various connections and put together and repeat the 4 different methods
No indications in Windows 10 Device manager
Questions, doubts and thoughts:
Is it possible in this state to access with ADB of a professional in order to perhaps clear the cache, resolve the issue without having access to recovery mode?
Should I simply try to purchase a new battery even though I never had any battery issues?
I am aware that a motherboard change will resolve it to the cheapest way possible but as I like to save the data such as different accounts this is not an option besides the phone is physically in good condition (never went under water or dropped). maybe to unsolder the flash memory onto a new mainboard as recovery mode might be part of the processor where the RAM is saved.
Any way to drain the entire phone further which may resolve the issue without loosing data. Similar in removing a CMOS battery on a PC mainboard and using a jumper.
Willing to pay and currently living in Europe.
UPDATE: Odin firmware performed by skilled professional member of xda forum, but still not working. EMMC issue which needs to be addressed with ISP in order to fix the issue. unfortunately I was told by local professionals that they do not have the tools for it. Therefor I wonder if someone knows someone who knows someone who can be of help. Location is Spain but Europe would also work.
UPDATE2: Got the phone back from technician who has experience with ISP but still same Error remains as to his conclusion that this is not an Exynos phone of which he has not the hardware tool to fix it and probably no one in Europe will have it.
Thank you very much in advance

Sorry... my english not so good...
so the point is whether you can enter recovery or download mode or not ?

Vuska said:
Sorry... my english not so good...
so the point is whether you can enter recovery or download mode or not ?
Click to expand...
Click to collapse
I am able now to enter download mode.

snakebite3 said:
I am able now to enter download mode.
Click to expand...
Click to collapse
and do you able to flash stock again ? (newest one, because we cant downgrade the bootloader)...

Vuska said:
and do you able to flash stock again ? (newest one, because we cant downgrade the bootloader)...
Click to expand...
Click to collapse
Thank you for following up.
these ones were tried out:
Samfw.com_SM-G975F_DBT_G975FXXS9DTI8_fac
Samfw.com_SM-G975F_DBT_G975FXXU9FUCD_fac
Samfw.com_SM-G975F_XSG_G975FXXU9FUBD_fac
I am not sure but that person who helped me remotely may explain better

According to technician its Qualcomm Snapdragon which can only be fixed with the right tools. Not in europe.
I been getting different information and do require some expertise if someone can please help me

any further advice, input or suggestion?

I also Own Samsung S10+.
its showing the same thing.
tried Flashing Via Odin it failed.
Tried to enter Recovery Mode but also failed to enter recovery mode.

OMG. I thought I was the only one in the world. I sent it yesterday to a data recovery technician to see what they will do since according to some insider in order to recover the data they would have to access the phone and fix the boot of which the problem get solved itself since they can not remove the memory chip itself as it would get ruined. They will diagnose the problem first before they do anything. Obviously a mainboard change would be the easiest but thats not an option.
Was your phone also updated to UI Android 3.0?
How did it happen if I may ask?
I wont give up since my phone is physically totally fine.

Update from a data recovery company its communication:
What we tried to do in order to recover your device's data was to load through the phone's bootloader (in Download Mode) a software agent that allows us (in some cases) to transfer the data stored in the data partition. This software agent has been developed by us together with some of our partners and as we are sure you will understand we cannot give you more details about what this particular software does or how it does it, since this information is covered by professional and business secrecy.
In this case the phone's firmware was damaged to a degree that made it impossible for the information to be accessed with this software.
At this moment, we doubt the data could be recovered by any software available now in the market. That's our opinion, but you can of course send it to other companies to see if they can recover it.
Since I am not the only one anymore with the same issue I recommend for people to come forward in order to get help

So far there is a tool needed to reprogram EMMC but I dont know which tool neither do I know where to find that person with this knowledge

snakebite3 said:
So far there is a tool needed to reprogram EMMC but I dont know which tool neither do I know where to find that person with this knowledge
Click to expand...
Click to collapse
Your device is powered by Snapdragon or Exynos?

LinhBT said:
Your device is powered by Snapdragon or Exynos?
Click to expand...
Click to collapse
I honestly dont know anymore since numerous people said contradicting things.
I am under the impression it is Exynos as of the research of the model SM-G975F/DS

Need to know exactly if it's Snap or not. If it is, then there're 2 options you can try.
1. Ask some one have the same device model as you, do a ROM dump ( you can google for more detail ). Once you got that, I can share with you the tool needed for restore your device from that dump.
2. Try find your device's Factory Images ( similar to Fastboot ROM, but a little different ), and an authenticated prog of your SoC ( this I can share too if you choose this option ) then boot your device into EDL mode by using fastboot2EDL script ( on Git, you can google too ) then use QFIL ( one tool in QPST Tools by Qualcomm ) and force flash the images into the device.
So far as my experience and understanding, there're only these 2 solutions to fix your device ( if it's Snap powered ).

According to the seller: "The phone is Taiwanese version and CPU should be Exynos 9820"
Maybe someone can help me please.. still

If its Exynos powered, then I have no solution for it. Sorry bro!!!

LinhBT said:
If its Exynos powered, then I have no solution for it. Sorry bro!!!
Click to expand...
Click to collapse
Thank you for your reply.
Can you please explain me why and who I should be looking for.

Anyone has knowledge how to fix this issue, please? USA based

LinhBT said:
Need to know exactly if it's Snap or not. If it is, then there're 2 options you can try.
1. Ask some one have the same device model as you, do a ROM dump ( you can google for more detail ). Once you got that, I can share with you the tool needed for restore your device from that dump.
2. Try find your device's Factory Images ( similar to Fastboot ROM, but a little different ), and an authenticated prog of your SoC ( this I can share too if you choose this option ) then boot your device into EDL mode by using fastboot2EDL script ( on Git, you can google too ) then use QFIL ( one tool in QPST Tools by Qualcomm ) and force flash the images into the device.
So far as my experience and understanding, there're only these 2 solutions to fix your device ( if it's Snap powered ).
Click to expand...
Click to collapse
Hi mate, My phone is Snapdragon powered..
My problem is almost similar.. But not exactly.. After almost 2 months I am not able to find a solution.. But after this period of researching and googling about things related to my problem.. I feel now, either any one of the following is the cause of problem:
1. Emmc is stuck or locked in read-only mode `(Can move files from pc , delete already present files anywhere in any directory, but all changes vanish after reboot... all file and directory structure remain intact- moved files from pc gets deleted.. and deleted files which were already present come back after reboot )
2. Corrupted /data and /cache partition, as e2fsck in twrp terminal results shows "filesystem still has errors" and "e2fsck: unable to set superblock flags on /dev/block/mmcblk0p** ) in both these file system (I think they are preventing flashing procedures- Odin stock firmware flashes and twrp custom ROM flashes both are successful, but after reboot no changes can be seen... - Even Recovery.img and boot.img flashes don't seem to work even both are shown successfully flashed in twrp) After reboot current version twrp boots again instead of newly flashed different version recovery.img ... same with boot.img even after running magisk uninstaller zip files.. running uninstall.zip 2nd or 3rd time also shows magisk patched image detected in log which should be removed in 1st iteration itself..
3. Might be magisk is preventing these changes to be made.. or It might be the /System_root creation as mountpoint for system partition which used to be previously /system normally. This might be the superblock creation which not used to be there
My Samsung's twrp and Download Mode seems to be working but no changes made by them even after successful operations by both.
Can you suggest anything? You can look my thread as to get even more detailed overview of what's happening and whatever I'have tried here - https://forum.xda-developers.com/t/...t-not-changing-anything-after-reboot.4462639/
You can see my attachments in my above thread to see my directory structure of system_root and my download mode pictures and odin system ROM flash pictures.

LinhBT said:
Need to know exactly if it's Snap or not. If it is, then there're 2 options you can try.
1. Ask some one have the same device model as you, do a ROM dump ( you can google for more detail ). Once you got that, I can share with you the tool needed for restore your device from that dump.
2. Try find your device's Factory Images ( similar to Fastboot ROM, but a little different ), and an authenticated prog of your SoC ( this I can share too if you choose this option ) then boot your device into EDL mode by using fastboot2EDL script ( on Git, you can google too ) then use QFIL ( one tool in QPST Tools by Qualcomm ) and force flash the images into the device.
So far as my experience and understanding, there're only these 2 solutions to fix your device ( if it's Snap powered ).
Click to expand...
Click to collapse
any tips here?
S20 FE bootloop after security update
So I never posted here but I usually pass by some topics so sorry for any mistake in creating this discussion. Today I deleted some stuff from my S20 FE and downloaded via OTA the march security update in my device, then I was caught by surprise...
forum.xda-developers.com