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...
Hello guys
2 1/2 years with my D802 and in october i change rom because i have bootloop problem (Zip "kernel" for CM12 on CM13...) And... Slow charging appears (Actualy: Latest CM 13 Nightly )
Problem:
Not charging when boot in android in 99% of times, and randomly 10-1500mA charging when i have luck
Charging slow phone Off and in TWRP but it's random, sometimes nice charging ( 200mA-1500mA )
No USB connection when Android is on ( No MTP, ADB, Charge, no Windows sound ) (i use ADB wifi) but USB is okey in TWRP ( No adb but MTP ok and charging ok sometimes )
What i tried:
Other AC Power
Other USB Cable
Other Rom ( Newest CM 13 Nightly with System/Dalvik/Cache Wipe )
Other Kernel ( Lambda Infinito Stable and Beta N9 with "Fast charge" like Dorimanx Stock Kernel )
New battery ( 20euro in my a*s lol )
Clean the gnat in the usb port
What i don't try:
Go back to Stock Firmware
Change USB plug
If you have same problem solved, tell me please !
Thanks
I thinks i solved the problem...
I found a gnat in the usb port after cleaning it .-.
Phone charging... Nice solution
Edit: Big luck, the gnat don't was the solution
riwan15 said:
I found a gnat in the usb port after cleaning it .-.
Click to expand...
Click to collapse
Dafuq. Funny experience. How the hell does a gnat fit into this tiny hole. I Germany the gnats are up to 10mm long. I would have to mummify or dry it to decrease size. But nice that your phone is back in business.
Lol, phone at 100%, i disconnect the usb cable, wait for 99% and... Not charging again... Now i'm at 37% and crying x)
The solution don't was the gnat x) Only big luck lol
Maybe solution:
In TWRP (phone at 0% and plugged) the battery don't appear in the top (normal) but i disabled the MTP and the battery show up and charging ! I retry when the phone is a 0% and confirm this fix !
(Sorry if i alone or something but a pass 1week to search for fix and there is no fix in google, only "hardware" problem but i don't thinks the hardware problem exist if the phone don't touch water or has fallen)
I hope this thread is gonna help somebody
Maybe change TWRP version can fix the problem ? I'm gonna try it after looking if disable the MTP is a fix
Edit: TWRP from 2.8.6.1 to 3.0.2-1 (Blastagator's TWRP) fixed half of the problem, now 1/2 charging phone off and always in recovery, left phone with android on and the problem is fix :3
Problem "fixed"
The only way for charging is to plug when the phone is booting ( on lg screen, before recovery or android ) In recovery the charging is safe, in android boot i need sometimes to plug/unplug after boot to start charging
The problem is now not really one for me, just a gesture to do ( Phone working, new battery = 2days phone on !! I'm happy like 2years ago)
For USB Data, no fix found, but Airdroid and ADB Wi-fi are in the party
I hope this thread can help
Info:
D802 - TWRP 3.0.2-1 - CM13 Nightly Dec 03 2016 - No kernel - Xposed V87
hi
I have xiaomi mi note 2 and updated this device .
but bluetooth not working after update A few months ago.
and wifi not working after new update . this update receive OTA
bluetooth is turned on but not detect any device.( in hardware test has mac address )
wifi is turned on and detect any wireless device but not connect to these devices.( in hard ware test has mac address and detect any devices)
i reset factory and full wipe . change rom by global , stable , developer , china , europe , custom ,.... but not solve this problem
PLEASE HELP ME .
You can try to install the global stable with fastboot.
Before doing this , make a backup because this will erase your entire storage.
I think you need to have adb and fastboot installed on your PC , not sure.
Download the fastboot rom from here: http://en.miui.com/a-234.html
You can find it in the fastboot method section.
Unzip the archive and double click on flash all.bat
Put your phone into fastboot mode and plug it in.
It should take a while , so relax.
It should close the console when it's done , if i'm not wrong.
Boot into the os and test wifi and bluetooth now.
Hope this will help , this is all i can say that it might work
ok . thank you for reply
I used these ways and not working in my device .
my phone should repair and change wifi and Bluetooth IC .
wifi and Bluetooth IC in my phone is ruined and should change by another IC
I haven't good news for you, probably motherboard it's broke. WiFi and Bluetooth it's first symptoms. My tip, try found mi note 2 with broke OLED, motherboard is cheaper than display.
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
Hello, recently I came across this strange issue on my Redmi note 7 ( Lavender ) where certain custom roms will just literally stop their boot process midway and the device shuts down inspite of having a fully charged battery. The roms will only boot up normally when my device is connected to a wall adapter or via the usb cable plugged in to my computer. Lineage os v18.1 was the only custom rom as of now which booted normally. Can anybody tell me why is this issue happening and if there is any fix for this strange issue ?
Thanks
Edit
Lineage os v18.1 shuts down all of a sudden without any warning. Even stock MIUI won't boot unless I connect a power source to the device. Also I tried all the known ways of decrypting after flashing Orange fox recovery but no matter what I do, the encryption stays there and I have to format 'data' once or twice to boot up. Lazy flasher dm-verity-opt-encrypt doesn't work. I flashed the latest one from here . Magisk works but doesn't disable force encryption. OTA and dm-verity options from Orange fox recovery doesn't work. This issue is really big. I searched google for possible fixes but none of them were properly related to the issues i am having and not all of the options are specific to my device. Any help will be appreciated !!
Thanks
[email protected] said:
Hello, recently I came across this strange issue on my Redmi note 7 ( Lavender ) where certain custom roms will just literally stop their boot process midway and the device shuts down inspite of having a fully charged battery. The roms will only boot up normally when my device is connected to a wall adapter or via the usb cable plugged in to my computer. Lineage os v18.1 was the only custom rom as of now which booted normally. Can anybody tell me why is this issue happening and if there is any fix for this strange issue ?
Thanks
Edit
Lineage os v18.1 shuts down all of a sudden without any warning. Even stock MIUI won't boot unless I connect a power source to the device. Also I tried all the known ways of decrypting after flashing Orange fox recovery but no matter what I do, the encryption stays there and I have to format 'data' once or twice to boot up. Lazy flasher dm-verity-opt-encrypt doesn't work. I flashed the latest one from here . Magisk works but doesn't disable force encryption. OTA and dm-verity options from Orange fox recovery doesn't work. This issue is really big. I searched google for possible fixes but none of them were properly related to the issues i am having and not all of the options are specific to my device. Any help will be appreciated !!
Thanks
Click to expand...
Click to collapse
That means your battery is done for, even if your battery show good health there's limit on how much Amp. your battery can produce while booting which is insufficient, so better replace battery