This device probably reached wear estimation for eMMC flash memory (eMMC wear-out). Backup your data that device will reach end of its life soon.

try twrp+magisk+patch if it had bootloader unlocked take it to service centre - they can restore stock rom for free

The problem with /data has now been fixed. I had forgotten that in the past, I was trying the OrangeFox dual-boot recovery on this device, and it had repartitioned /data. I fixed this by flashing the appropriate *.img files again for my OS (OOS 10.3.8), and then by booting into the standard OrangeFox recovery (the non-dual-boot version) via fastboot, and then by using its adb sideload facility to flash that same OrangeFox recovery. OrangeFox's adb sideload mechanism offers options to the user for repartitioning and rebuilding /data. I utilized those options and set /data back to "Stock", and after that, /data became accessible again, and I could format it and access it in recovery with no problem. At this point, I flashed OOS 10.3.8, and I then flashed the appropriate TWRP and Magisk. Now, my device is back up and running in that OOS version. The EDL problem continues, but given that my device is now usable again, I am not overly concerned about this MsmDownloadTool issue at the moment. In my spare time, I'll continue to look into that. All's well that ends well! ... and now it's indeed a happy New Year for me!

You could try to flash all partition images (except userdata.img) via heimdall command line heimdall flash --BOOTLOADER sboot.bin --CM cm.bin --PARAM param.bin --BOOT boot.img --RECOVERY recovery.img --RADIO modem.bin --SYSTEM system.img --CACHE cache.img --HIDDEN hidden.img The above example command is created from partition list. This is how you get pit file install https://www.glassechidna.com.au/heimdall , https://www.python.org and https://www.xda-developers.com/samloader-download-updates-samsung-galaxy download and decrypt stock ROM for your region code C:\Android\samloader>samloader -m SM-N920C -r AFR checkupdate N920CXXS5CRH1/N920COJV4CRB3/N920CXXU5CRH1/N920CXXS5CRH1 C:\Android\samloader>samloader -m SM-N920C -r AFR download -v N920CXXS5CRH1/N920COJV4CRB3/N920CXXU5CRH1/N920CXXS5CRH1 -O . downloading SM-N920C_1_20180820163853_vvggswhd8u_fac.zip.enc4 [################################] 38453/38453 - 00:06:20 C:\Android\samloader>samloader -m SM-N920C -r AFR decrypt -v N920CXXS5CRH1/N920COJV4CRB3/N920CXXU5CRH1/N920CXXS5CRH1 -V 4 -i SM-N920C_1_20180820163853_vvggswhd8u_fac.zip.enc4 -o SM-N920C_1_20180820163853_vvggswhd8u_fac.zip [################################] 615247/615247 - 00:01:21 unpack files from zip C:\Android\samloader>7z l SM-N920C_1_20180820163853_vvggswhd8u_fac.zip 7-Zip 18.01 (x64) : Copyright (c) 1999-2018 Igor Pavlov : 2018-01-28 Scanning the drive for archives: 1 file, 2520047837 bytes (2404 MiB) Listing archive: SM-N920C_1_20180820163853_vvggswhd8u_fac.zip -- Path = SM-N920C_1_20180820163853_vvggswhd8u_fac.zip Type = zip Physical Size = 2520047837 64-bit = + Characteristics = Zip64 Date Time Attr Size Compressed Name 2018-08-20 16:39:50 ..... 5058737 1491256 BL_N920CXXS5CRH1_CL11762721_QB19211222_REV00_user_low_ship.tar.md5 2018-08-20 16:39:50 ..... 4797583545 2248597336 AP_N920CXXS5CRH1_CL11762721_QB19211222_REV00_user_low_ship_meta.tar.md5 2018-08-20 16:44:16 ..... 38092989 38093065 CP_N920CXXU5CRH1_CP10334463_CL11762721_QB19211222_REV00_user_low_ship.tar.md5 2018-08-20 16:44:18 ..... 273756344 231865000 CSC_OJV_N920COJV4CRB3_CL11762721_QB16863364_REV00_user_low_ship.tar.md5 2018-08-20 16:44:18 5114491615 2520046657 4 files extract pit from CSC file CSC_OJV_N920COJV4CRB3_CL11762721_QB16863364_REV00_user_low_ship.tar.md5 inspect NOBLELTE_EUR_OPEN_HIDDEN150M.pit pit file with https://forum.xda-developers.com/showthread.php?t=1916936 or https://forum.xda-developers.com/showthread.php?t=2953072

Remove the SD card when, that will stop the bootloop. When you've booted up again, insert the SD card and continue as usual

I was able to get this phone working again by unplugging from the wall and letting it continue bootlooping until the battery was dead. I then let it sit for a day to ensure it had no power left. I then charged via USB on my PC (NOT A WALL CHARGER) until it was fully charged. I then powered it up and it seems to be working okay so far.

assuming you have patched the whole rom AP_[device_model_sw_ver].tar.md5 (not only boot.img) according to https://topjohnwu.github.io/Magisk/install.html#instructions (to avoid discrepancies in several fstabs), start from scratch again. this time try preserve force encryption in Magisk settings to avoid issues with encryption. after factory reset userdata encryption should work again. Of course as always don't forget to deactivate https://topjohnwu.github.io/Magisk/install.html#unlocking-bootloader before flashing custom binaries

I am not sure what you ask for but The CWM Recovery saved my data, How can I view it? if you mean backups, they'd be in your SD card. Fastboot cmd>Fastboot flash system system.img < Waiting for Device > !! that usually means a driver problem IF you can boot into bootloader properly. Interesting link with un-bricking guide

You could try booting into Safe Mode (according to this article you should be able to do so by holding down the Vol - key while switching on the device with the Power button). In safe mode, all user-installed apps are "disabled", so they won't be started automatically. Once in safe mode, remove the troublesome app (uninstall it via Settings → Applications → Manage Applications). Then simply reboot to leave safe mode -- your device should now boot up fine.

Enter recovery and delete dalvik/cache. To enter recovery you have to hold Volume up + Home + Power (The same with Volume down is download mode). Once in recovery, select the option to wipe cache/dalvik, then restart the phone. If the phone keeps rebooting as it was doing before, try searching the log of the boot sequence to see if you can find where it fails. You will need a PC with Android SDK installed and the phone's USB cable. With the phone off, open a CMD window in your PC, go to Android SDK directory and run adb logcat Turn on your phone and connect the USB cable. You should en seeing in your cmd window the log of the phone as it boots. Once it enters a boot loop, you should be able to check the log and see what it tries to do and can't do (that triggers the boot loop).

How to boot into safe mode: Note: Not all devices support safe mode While your device is booting up, hold down the Home button. This should be done right after the screen starts up, before the boot animation does, and should be held until the device fully boots. Once done, you should see the words 'Safe Mode' in the bottom left corner. How to Factory Reset/Clear Userdata If booting into safe mode didn't work, or your device is still boot looping after removing some of the apps that are using the greatest memory, you will have to erase your data. You should be able to access stock recovery by holding down the Volume UP button, the Home Buton and the Power button until the device finishes booting into recovery mode. From here you can use the volume keys to navigate to the wipe userdata option, and press the power button to select it. Once done, press the back key to go to the main menu and select to reboot the device now. This will erase all userdata on the device! If it still doesn't work? If it still doesn't work after following these steps, then you will have to take it to a repair center, sorry!

Its a faulty phone. Take it back and get a new one. But you can turn off mobile data and it will stop rebooting. or search google for "Motorola Defy+ Rebooting" for other opinons

It seems that the HTC Desire models are known to have hardware that easily gets defective... I've searched far and wide, and the general consensus seems to be that if a restore and/or factory reset doesn't resolve the problem, then it's not a software issue but a hardware defect. The device could probably be repaired, but if the warranty gone then it's probably wiser buying a new device instead.

Try booting while pressing the back key. That will get you into fastboot, and you can access hboot (and hence recovery) from there. If it worked try any solution among this.. It depends on the cause of the boot loop Wipe cache and dalvik (depending on what recovery you look in different places for these. I think ClockworkMod may have wipe dalvik in advanced). TBH I think this is unlikely to do it, but is harmless. If something has been corrupted in the ROM then reflashing the ROM (without wiping) will fix it. If it's data corruption then a factory reset will do it.

If you have a bootloop (samsung logo looping), it is because you messed up the rooting procedure. I had this problem when I tried to root a relative's Ace. Since you've tried factory reset and it doesn't work, enter recovery mode and do factory reset. (recovery mode: press and hold volume down + power button for 15 seconds, navigate up/down by volume button and power button to select). Reboot and see if it fixes the issue. If it does not, there are two options: flash CWM from recovery (here's the CWM zip file to flash from stock recovery), then reboot to CWM and install a custom ROM. This is what I did, as I wanted to load CM7 anyway. If you want stock, download Odin, get stock firmware from sammobile.com or XDA forums (look for Developmet section under your device specific forum) and flash it.

If you've just plugged it in to the charger, leave it a while before you try to turn it on. The boot sequence uses power faster than USB can provide it, so you will need a little juice in the battery in order for it to boot up all the way.

Sometimes android goes into Fubar mode and the only way to get past it is to make a hard reset. This unfortunately deletes any data stored on the device but anything stored on the memory card will remain. Luckily there is a hardware hard reset mode. A hard reset can be accomplished by doing the following things: Turn the power off. If your Samsung Galaxy S II is frozen, pull the battery out and reinsert it Hold the Volume Down button Press and release the Power button You are now presented with a menu that allows for Fastbook, Recovery, Clear Storage, and Simlock Select Clear Storage by pressing the Volume Down button Press and release the Power button Now simply confirm your decision: Volume Up for YES and Volume Down for NO Some versions of samsung galaxy s2 require that you need to hold down volume down AND volume up to get into the menu. Youtube video showing how it's done

If it starts to boot (goes to the boot logo/animation) or Recovery/Download mode at least tries to load, then the motherboard is NOT damaged. Your device is soft-bricked, and just needs to have a compatible ROM flashed, and your userdata erased for your device to be fully functional again. The person is the service centre doesn't know what hey is talking about (I wouldn't trust those people - they just want your money).

I don't think anything can be done at this point, you should've been more careful when you messed with Android System itself. If it was SystemUI your phone would reboot into system, but unfortunately that ain't the case. The only reasonable thing to do would be flashing a new ROM. ADB won't work until your phone reboots to system. I don't think fastboot will help you either, so that leaves only one option, flash it. Next time you try to change either "framework-res.apk" or "SystemUI.apk" try this script. It will get the job done without any mess. Remember to run the script as root and put the apk files in external sdcard(extsd). #!/system/bin/sh mount -o rw,remount /system if [ -f "/extsd/framework-res.apk" ] then cat /extsd/framework-res.apk > /system/framework/framework-res.apk chown 0.0 /system/framework/framework-res.apk chmod 0644 /system/framework/framework-res.apk else echo "Error: File(s) not found." fi if [ -f "/extsd/SystemUI.apk" ] then cat /extsd/SystemUI.apk > /system/priv-app/SystemUI.apk chown 0.0 /system/priv-app/SystemUI.apk chmod 0644 /system/priv-app/SystemUI.apk else echo "Error: File(s) not found." fi reboot

Please erase all data and the dalvik-cache (if you have recovery). Are you using the stock or custom ROM? This looks to me like a bug in the ROM to do with NFC - this is the only reason the device would lock up like that. If you are using a custom ROM, I suggest you contact the ROM developer with the logs, if not, check for a software update. EDIT: The NFC service will only run if NFC is enabled - if you disable it, and then reboot, it should no longer be active. If it is you can kill it via Settings->Apps->Running.