Related
This morning, my phone will not boot. Black screen, no lights, no vibration, no logo.
I suspect it had something to do with me using mmcblk0p3 as a swap partition via Swapper2 the night before, or the Purity kernel I installed for overclocking (although it was stable with overclock for several boots).
The former was the most likely cause.
I searched for what the purpose of mmcblk0p3 was for, but I was sure it was used as Linux swap.
I couldn't even boot into recovery nor fastboot.
Any help guys?
Hi!
Try to connect your phone (without battery) via a USB cable to the KDZ Flash Tool by pressing volume + and power. Appears on the screen Emergency Mode with a yellow background. Install new software. If you don't know how to install new software, this guide will help you.
http://forum.xda-developers.com/showthread.php?t=2167344
Poland_Developers said:
Hi!
Try to connect your phone (without battery) via a USB cable to the KDZ Flash Tool by pressing volume + and power. Appears on the screen Emergency Mode with a yellow background. Install new software. If you don't know how to install new software, this guide will help you.
http://forum.xda-developers.com/showthread.php?t=2167344
Click to expand...
Click to collapse
I've already tried that, doesn't work.
Oh, I forgot to list my phone's specs.
LG P705G
Cyanogenmod 10 with 4cyl Turbo Engine/Crossbreeder and AC!D audio engine
Swap enabled
Probably motherboard is defective... The battery is charging at all?
Checked battery level manually with a voltmeter.
Fully charged, and the phone is plugged in anyways right now.
The charging animation doesn't show, though.
Maybe give him the guarantees...
UPDATE: Please see bottom of post
Hi all,
Quick disclaimer, I'm not an expert in phones, the Mi A1 is my first smartphone, and LineageOS is the only operating system I've used. However, I'd like to think I have a good grasp of computers, so I'll provide as much infomation as I can to help debug the problem.
I updated my Mi A1, via the settings menu within LineageOS itself. This was done this morning, so I assume it was the latest update (nightly 15.1 lineage-15.1-20190118-nightly-tissot-signed, as listed at download.lineageos tissot. The update downloaded, installed, and asked me to reboot the phone. It rebooted, and asked for my pin to start. I entered the pin, then left the room. When I returned, the screen was black, I now cannot turn on the phone via the power button, nor are there any signs of life when pressing volume+button. No LEDs are blinking when attached to a charger, or a computer via USB. As far as I can tell, its just a piece of plastic and glass.
I have connected this to my computer, and attempted to detect the phone. Using adb, I am not able to recognise the phone:
Code:
adb devices -l
Gives:
Code:
List of devices attached
Device manager detects a USB storage device, which is promising I guess:
Code:
QUSB_BULK
I am unsure how to proceed with solving this. After searching around, this reddit post (r/LineageOS/comments/adhfdq/updated_lineage_os_on_moto_x4_now_the_phone_wont/) seems to be the most similar (albeit for a Moto X4), as other posts on this forum seem to describe problems where the phone is at least partially active.
I would really appreciate any help that can be offered. I don't mind doing a total wipe of the phone, as long as I can find a way of backing up the existing files.
regards,
B
Update: After a while, I just held down the power button and it turned on like nothing had happened. I'm very confused, I can only think that perhaps it was a mechanical fault on the power button? I'll leave this post up here for now just in case it fails again, but if the mods want to delete this post, please feel free to. Sorry if I wasted anyones time.
Not sure how to title this forum post, but this is the best I got. Forgive my ignorance and lack of knowledge on these topics.
I was trying to root my Axon 7 mini. After some searching to find out how to unlock the bootloader (like needing JDK, older Android SDK version to run android.bat, etc.), I finally got it to work. Ran Recovery to "apply update from SD Card" (can not remember the file right now) and was then ready to load TWRP Recovery. When I rebooted to the recovery TWRP image, it told me something failed and the phone had to be factory reset. I took my SD card out in fear of my data being deleted and "accidentally" clicked the power button. It then reloaded with a password prompt where I typed some random password (1234 because I never set a pin password nor knew what to do here), clicked submit, and then gave me some error; now my phone doesn't work.
The Problem:
- I can enter bootloader, sometimes, but can only run fastboot commands; adb device does not detect phone so can't run adb commands (always says the server is old or something and reloads daemon successfully but never finds my device regardless). Also, I don't think I can get it to run in EDL mode; MiFlash gives out errors too when trying to flash recovery images.
- Recovery mode doesn't appear or work; not sure if the MiFavor command prompts on the phone is recovery or not, but it's safe to say this no longer appears. This is also where I believe the phone bootloops. I can get the fastboot commands to flash a TWRP recovery, but it never actually enters the TWRP dashboard.
- Can not turn off the phone... I think. None of the command options that appear on-phone shut it off; however, when the screen does stay black, I'm not sure if it's in EDL mode or plainly off.
- Device Manager shows the phone as different stuff (namely Kedacom USB Device and Portable Devices/MTB USB Device). Sometimes Qualcomm appears, but it depends. More often than not, when my device does appear, there's either an error code (like Code 10, Code 43) and/or the device is grayed out.
Conclusion:
I just want to get my phone to work normally again, if possible. Currently, I locked the oem to see if fastboot commands could still work and now I'm stuck at the ZTE logo, so can't try to unlock it right now. What are the proper tools, drivers, programs, etc I need to get this phone back to normal? I've scoured the web and these forums for 2 days now with no luck and lots of either missing info or obscure info.
I bought this at Best Buy, so I'm assuming it's US Axon7 Mini version in terms of drivers (not sure if the box specifies any info that could be useful here).
Un-brick Axon 7 Mini
Dear all,
I experienced the same issue with my phone after I tried to flash it with custom ROMs and recovery.
I thought I lost it as I was not able to enter adb mode (not recognized on the PC) or even not able to enter EDL mode with the button combination so not able to do anything with it.
Only watch it boot and display the ZTE logo.
After some research, here is what I had to do to get it recovered.
First thing you need to get is an EDL cable.
I let you search on your favorite site. Mine was a Generic eDL Deep Flash Qualcomm 9008 Cable 2 in 1 for Z3 X/Octopus.
Until you receive it, make sure you have the latest Qualcomm drivers installed on your PC.
You can find it easily.
Then, connect your phone and your PC with the EDL cable.
Press the button on your EDL cable (there should be one) for a few seconds and keep it pressed.
Then, press the power button and keep it pressed for at least 20 seconds.
At this stage, you should have both buttons pressed and after some time, you should feel the phone rebooting.
After 20 seconds, release the power button.
Then, after 10 other seconds, release the EDL cable button.
At this stage, your phone screen should stay black and your phone should appear in the device manager as Qualcomm USBHUB (or somehting similar)
You are in EDL mode and should be able to perform a recovery flashing using tuliptool.
Then I followed the steps I found here:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
If you are still stuck, pm me.
Be patient, all will be fine,
mariegalante55 said:
Dear all,
I experienced the same issue with my phone after I tried to flash it with custom ROMs and recovery.
I thought I lost it as I was not able to enter adb mode (not recognized on the PC) or even not able to enter EDL mode with the button combination so not able to do anything with it.
Only watch it boot and display the ZTE logo.
After some research, here is what I had to do to get it recovered.
First thing you need to get is an EDL cable.
I let you search on your favorite site. Mine was a Generic eDL Deep Flash Qualcomm 9008 Cable 2 in 1 for Z3 X/Octopus.
Until you receive it, make sure you have the latest Qualcomm drivers installed on your PC.
You can find it easily.
Then, connect your phone and your PC with the EDL cable.
Press the button on your EDL cable (there should be one) for a few seconds and keep it pressed.
Then, press the power button and keep it pressed for at least 20 seconds.
At this stage, you should have both buttons pressed and after some time, you should feel the phone rebooting.
After 20 seconds, release the power button.
Then, after 10 other seconds, release the EDL cable button.
At this stage, your phone screen should stay black and your phone should appear in the device manager as Qualcomm USBHUB (or somehting similar)
You are in EDL mode and should be able to perform a recovery flashing using tuliptool.
Then I followed the steps I found here:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
If you are still stuck, pm me.
Be patient, all will be fine,
Click to expand...
Click to collapse
I had a feeling an EDL cable was my only option left given everything I've looked up and the multiple methods I've tried. Wanted to avoid spending money on one but doesn't look like I have a choice given the circumstances - oh well. Regardless, thank you for the response and advice. Have to wait a while, though, to get the cable and test to see if this works.
If anyone else ever ends up in the same royally screwed situation as me, getting an EDL cable - or DIY one if you wanna be cheap and are confident enough to do so - is probably your saving grace.
Kuma21 said:
I had a feeling an EDL cable was my only option left given everything I've looked up and the multiple methods I've tried. Wanted to avoid spending money on one but doesn't look like I have a choice given the circumstances - oh well. Regardless, thank you for the response and advice. Have to wait a while, though, to get the cable and test to see if this works.
If anyone else ever ends up in the same royally screwed situation as me, getting an EDL cable - or DIY one if you wanna be cheap and are confident enough to do so - is probably your saving grace.
Click to expand...
Click to collapse
K, I can get tuliptool to work and run command, but i keep getting a "Failed: Unkown Error" response everytime i run a command. Can't unlock my bootloader, nor write a recovery disk due to this error. does anyone have any idea why this happens?
Can anyone with this device provide the exact steps to unlock the bootloader. I have tried the many ways offered via google search and none seem to work. I have USB debugging and OEM unlock allowed in the device settings. I can boot into the bootloader via keys and using ADB. I've tried various key combos to get to the page (supposedly available) that allows one to switch the bootloader from locked to unlocked - no luck.
All help appreciated.
Do you mean that the command fastboot oem unlock doesn't work?
Note that: Unlocking bootloader wipes all device's data!
XDHx86 said:
Do you mean that the command fastboot oem unlock doesn't work?
Note that: Unlocking bootloader wipes all device's data!
Click to expand...
Click to collapse
Thanks for your reply and new suggestion. No that does not work either. I go to bootloader download mode, enter the command "fastboot oem unlock" and get "waiting on device". I am connected to the device as I get a response when queried "adb devices". Any other thoughts/suggestions?
[email protected] said:
Thanks for your reply and new suggestion. No that does not work either. I go to bootloader download mode, enter the command "fastboot oem unlock" and get "waiting on device". I am connected to the device as I get a response when queried "adb devices". Any other thoughts/suggestions?
Click to expand...
Click to collapse
You're supposed to boot the device to fastboot/bootloader by adb reboot bootloader not download mode.
Also to detect the device in fastboot the command is fastboot devices
Please if you're new to this stuff then don't do it. May I ask why you're trying to unlock bootloader?
XDHx86 said:
You're supposed to boot the device to fastboot/bootloader by adb reboot bootloader not download mode.
Also to detect the device in fastboot the command is fastboot devices
Please if you're new to this stuff then don't do it. May I ask why you're trying to unlock bootloader?
Click to expand...
Click to collapse
Again, thanks for your reply. I have previously installed Lineage on a Fire HD8. So not quite a newbie but everyone is new once - right? I am trying to install Lineage on this SM-T290.
The command "fastboot devices" is not returning anything but "adb devices" does which leads me to believe my hardware connections are correct. "adb reboot bootloader" does take me to the bootloader but it indicates download mode.
I suspect I am missing something simple. Your help is appreciated. Thanks
You need to enable OEM unlock and debugging mode first. And make sure the PC is allowed to debug on your phone.
Also if fastboot command doesn't return anything then most likely you need the correct device driver, you can get it from here.
Alternatively you can try this method:
Boot to download mode.
Long press volume up. This will wipe your data and automatically reboot.
After reboot you should have unlocked bootloader and OEM unlock option greyed out in the settings.
Installing custom ROM doesn't make your device better.
XDHx86 said:
You need to enable OEM unlock and debugging mode first. And make sure the PC is allowed to debug on your phone.
Also if fastboot command doesn't return anything then most likely you need the correct device driver, you can get it from here.
Alternatively you can try this method:
Boot to download mode.
Long press volume up. This will wipe your data and automatically reboot.
After reboot you should have unlocked bootloader and OEM unlock option greyed out in the settings.
Installing custom ROM doesn't make your device better.
Click to expand...
Click to collapse
Thanks but still no go.
I have enabled usb debugging and enabled OEM unlock (both done previously)
I have (had) installed latest drivers previously
adb devices returns my unit data
adb reboot bootloader command puts device in "download mode !!"
fastboot devices returns "waiting on device"
fastboot oem unlock also returns "waiting on device"
Attempted your alternative method, no go
I understand custom ROM doesn't make device better. I like the learning challenge. Hope you understand. Appreciate your help thus far and any other ideas you might have.
This is 100% driver issue, I already provided the driver link.
The device driver may be different from internet provided driver through windows device manager. Or the driver installed upon connecting the device.
XDHx86 said:
This is 100% driver issue, I already provided the driver link.
The device driver may be different from internet provided driver through windows device manager. Or the driver installed upon connecting the device.
Click to expand...
Click to collapse
Thanks. I had installed a driver from the link you supplied (there were a few options). I'll try others. I appreciate all your help!
Here's how I did it.
Enable Developer mode, usb debug, OEM unlock (you've already done those, by the sound of things).
Power the tablet OFF.
Have your USB cable plugged into the computer but NOT the tablet.
Hold the volume up AND volume down keys simultaneously, then connect the USB cable.
The tablet will vibrate and show a blue-green screen, with Warning at the top and a white triangle with an exclamation mark at the bottom. (This is different from download mode.)
From here, long-press volume up to go into device unlock mode. Follow the instructions.
Heeni said:
Here's how I did it.
Enable Developer mode, usb debug, OEM unlock (you've already done those, by the sound of things).
Power the tablet OFF.
Have your USB cable plugged into the computer but NOT the tablet.
Hold the volume up AND volume down keys simultaneously, then connect the USB cable.
The tablet will vibrate and show a blue-green screen, with Warning at the top and a white triangle with an exclamation mark at the bottom. (This is different from download mode.)
From here, long-press volume up to go into device unlock mode. Follow the instructions.
Click to expand...
Click to collapse
Thanks again but no luck. Let's start with some basics:
My device is a Galaxy Tab A SM-T290 8.0 2019 one UA core version 2.1
Android 10
When I, with power off, press both UP & DOWN volume keys simultaneously, wait a few seconds, insert the USB cable (already in computer), I get a vibration but then a circle with a lightning bolt that shows the battery charge status. The screen does not go blue-green and there is no warning.
I have tried releasing the buttons after the vibration and after I see the battery power circle. No change.
I continue to appreciate your help but feel I am missing something simple or my device is not same as yours.
Let me know if you have given up!
[email protected] said:
Thanks again but no luck. Let's start with some basics:
My device is a Galaxy Tab A SM-T290 8.0 2019 one UA core version 2.1
Android 10
When I, with power off, press both UP & DOWN volume keys simultaneously, wait a few seconds, insert the USB cable (already in computer), I get a vibration but then a circle with a lightning bolt that shows the battery charge status. The screen does not go blue-green and there is no warning.
I have tried releasing the buttons after the vibration and after I see the battery power circle. No change.
I continue to appreciate your help but feel I am missing something simple or my device is not same as yours.
Let me know if you have given up!
Click to expand...
Click to collapse
I see that your tablet has One UA core.
That may make a difference. I can't remember now where I saw it (somewhere on these forums), but I recall seeing that One UI Core is more locked down than the "ordinary" One UI version. Incidentally, I get the same response as you if I plug the tablet into a charger (not computer) while pressing both volume keys.
I'll mention at this point that I'm on the point of going back to stock and relocking the bootloader, because I've not been able to have a custom ROM or recovery and a screenlock (PIN, password, or pattern) at the same time, and no one seems to know any workaround for this. I'm starting to wonder if my tablet is somehow odd.
It's a nice piece of hardware, but a right pain to do any mods to, and Samsung's extra security "features" can cause problems.
Heeni said:
I see that your tablet has One UA core.
That may make a difference. I can't remember now where I saw it (somewhere on these forums), but I recall seeing that One UI Core is more locked down than the "ordinary" One UI version. Incidentally, I get the same response as you if I plug the tablet into a charger (not computer) while pressing both volume keys.
I'll mention at this point that I'm on the point of going back to stock and relocking the bootloader, because I've not been able to have a custom ROM or recovery and a screenlock (PIN, password, or pattern) at the same time, and no one seems to know any workaround for this. I'm starting to wonder if my tablet is somehow odd.
It's a nice piece of hardware, but a right pain to do any mods to, and Samsung's extra security "features" can cause problems.
Click to expand...
Click to collapse
Hey! Once again want to thank you for hangin' in with me on this. So, it seems we have slightly different machines. I purchased mine at COSTCO. They offer a lot of good stuff at low prices. I've noticed, however, they tweak their offerings a little bit so they can honestly say "you can't get this somewhere else." Perhaps the difference in our machines explains that.
I definitely had my unit plugged into the USB port on my computer, not a power supply.
My only purpose in attempting this was the satisfaction of doing it and having two tablets with different operating systems.
Thanks again for your help. All the best!
Here's the reference to One UI Core that I was thinking of: https://forum.xda-developers.com/t/root-for-sm-t290-tab-a-8-0-2019.3965624/post-84355183
I'm not based in North America, and the local market isn't big enough to have retailer-specific variants (or, at least, I've never heard of any), so I probably have a standard item. But from what I've read, specially locked-down items are reasonably common in the US. Which doesn't make it any less frustrating.
Heeni said:
Here's the reference to One UI Core that I was thinking of: https://forum.xda-developers.com/t/root-for-sm-t290-tab-a-8-0-2019.3965624/post-84355183
I'm not based in North America, and the local market isn't big enough to have retailer-specific variants (or, at least, I've never heard of any), so I probably have a standard item. But from what I've read, specially locked-down items are reasonably common in the US. Which doesn't make it any less frustrating.
Click to expand...
Click to collapse
I read the post and tried the extra step of holding the up volume key when the power screen came on. It also didn't work. Unless something new shows up, my quest to unlock this bootlocker is over. I'll find some other technical challenge to chase.
I had the thought of contacting Samsung to see if they would tell me how to do this. My unit is well out of warranty so why should they care? Likely they wouldn't tell me anything but .....
I'm on Denver CO. Where are you? In my work and fun travels I've had the opportunity to visit many parts of the world. Perhaps I've been to your country?
Again thanks for all your help. I could not have gotten as far as I did without it.
I'm in Auckland, New Zealand. It's a good place to live but not if you want cheap tech. Freight costs tend to be high.
Heeni said:
I'm in Auckland, New Zealand. It's a good place to live but not if you want cheap tech. Freight costs tend to be high.
Click to expand...
Click to collapse
Never been to New Zealand. On the bucket list as it seems a beautiful place to live. Been to your close neighbor Austrailia a number of times. Want to go there again to snorkel on the barrier reef. All the best!
[email protected] said:
I read the post and tried the extra step of holding the up volume key when the power screen came on. It also didn't work. Unless something new shows up, my quest to unlock this bootlocker is over. I'll find some other technical challenge to chase.
I had the thought of contacting Samsung to see if they would tell me how to do this. My unit is well out of warranty so why should they care? Likely they wouldn't tell me anything but .....
I'm on Denver CO. Where are you? In my work and fun travels I've had the opportunity to visit many parts of the world. Perhaps I've been to your country?
Again thanks for all your help. I could not have gotten as far as I did without it.
Click to expand...
Click to collapse
Try method below. It worked for me.
Root for SM-T290 (tab a 8.0 2019)
Hi guys, I just bought an SM-T290 for my wife and I was unable to find any info here about rooting it. As most Tab-A tablets "are here", can I use a guide (and twrp) for an older tablet for this newer model?
forum.xda-developers.com
bignikescar said:
Try method below. It worked for me.
Root for SM-T290 (tab a 8.0 2019)
Hi guys, I just bought an SM-T290 for my wife and I was unable to find any info here about rooting it. As most Tab-A tablets "are here", can I use a guide (and twrp) for an older tablet for this newer model?
forum.xda-developers.com
Click to expand...
Click to collapse
Holding vol up and down, with the tablet off, and plugging in the USB from PC to tablet, works. And it makes no difference which end of the cable you plug in last, so long as the buttons are already pressed before both ends are attached.
XDHx86 said:
Do you mean that the command fastboot oem unlock doesn't work?
Note that: Unlocking bootloader wipes all device's data!
Click to expand...
Click to collapse
You do not need a PC to unlock the bootloader. Turn off the device, then you will want to do Volume Up + Volume Down + USB Cable, and then Long Press Volume Up, and then press Volume Up again.
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