Phone stuck in bootloop/not booting - Apple iPhone 12 Questions & Answers

My phone was stuck in a bootloop. After entering DFU mode and attempting to reset my device over itunes, my phone randomly crashes after the "extracting software" stage (tried this over 7 times).
Is there a way to reset my device or make it function again?

Same issue here. When trying to update via iTunes from 15.4 to 15.5, it prompts an unknown error (9). Googling it, it says it could be a problem regarding the NAND… which error do you get? Any help on this?

Related

[Q] Help with unbricking LGE720

Hey folks,
its bricked due to FOTA (I think it stands for: firmware over the air) update. This means the phone downloads a firmware update without computer connection or further PC-Software. Alas it didn't work.
Situation:
Phone starts, displays LG Logo and after that an 'updating firmware' screen for about 1 sec before rebooting and doing it all over again.
What I tried to solve this:
set up a new Win 7 32 bit machine to try to unbrick it. (drivers didn't work correctly on 64 bit) at least the MCCI driver update didn't)
connected the phone with the PC in Emergency Mode (holding VOL_UP + VOL_DOWN + PWR while USB is connected)
downloaded B2CApp (LGSupport Tool) and installed the device drivers for Emergency mode.
disabled the Android(Modem) dirver
downloaded V10D_00.kdz from LG home page
using the phones IMEI and this link:
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=IMEI_NUMBER_GOES_HERE
This gave me this link
http://csmgdl.lgmobile.com/swdata/WDLSW/LGE720/ADEUBK/V10d_00/V10D_00.kdz
I'm German so this seems all right, but I'm no expert​
installed msxml
ran KDZ_FW_UPD_EN and tried CDMA in CS_EMERGENCY Mode
A bunch of magic happend until the phone restarts during the process and is right back where we started, if I put it back to Emergency Mode while KDZ_FW_UPD_EN is still running the process finishes, but to no avail.
The log of this try is attached.
Where I am stuck now:
phone:
runs in Emergency Mode
is recognized by KDZ_FW_UPD_EN as well es LG Support Tool
Flashing via KDZ_FW_UPD_EN finishes
Flashing yields no result.
What else did I try
download V10C_00.kdz, as well as V10A_00.kdz from LG site and tried those with same result as with V10D_00.kdz
tried 3GQCT Type instead of CDMA
Wild guesses by me:
I need a different KDZ_FW_UPD_EN version, maybe different dll. I got it from here somewhre in a LG P500 related topic.
I messed up the driver install or need a different driver
LG hates me personally and planted this whole brick specifically to get to me.
The device really is permanently bricked, so I did all I could and there is nothing more to do? That would be sad, I hope I'm wrong here.
Additional Info:
The phone is not rooted and has never before been flashed. It ran with the same stock firmware since it was unwrapped.
The phone was not interrupted by power-loss during FOTA update.
The [read phone information] tool from KDZ_FW_UDP_EN crashes every time, maybe this tells somebody where things go wrong
Any help is appreciated. Ask for more info, if you need it.
Update - What else did I try:
I got the LG Support Tool to flash the Emergency Recovery all by itself runs till 99% --> reboots --> still stuck in same ol' bootloop
reentering Emergency Mode from the bootloop makes the Emergency Recovery finish with 100%, no error, but still bricked.
Regards
gimmeg

Borked my Cyanogenmod installation - please help! (LG Nexus 5x)

This was totally my fault but now I'm stuck. Any help would be greatly appreciated.
I just bought 2 nexus 5x phones and planned to install Cyanogenmod 13 on each. I succeeded on the first attempt but this is what happened on the second:
I forgot to re-enable USB debugging after unlocking the bootloader but managed to proceed with installing twrp and vendor.img. When it came time to push (adp push) cm13 to /sdcard, adp gave me this error: "adp: error: connect failed: no devices/emulators found". "fastboot devices" shows that the phone is connected and the recover mode screen shows fastboot mode. (Sorry, can't post a link to the install instructions because this is my first post).
I can get into twrp but trying to boot the phone normally does not work. I get an error saying that the device is corrupted, and then the boot hangs at the weird google animated logo. The screen never shuts off and the animated logo just keeps going around and around.
I can't do a hard reset because I keep ending up at twrp when I try to follow the hard reset instructions.
What should me next steps be?
Thanks.
Solved!
mrevans.info said:
This was totally my fault but now I'm stuck. Any help would be greatly appreciated.
I just bought 2 nexus 5x phones and planned to install Cyanogenmod 13 on each. I succeeded on the first attempt but this is what happened on the second:
I forgot to re-enable USB debugging after unlocking the bootloader but managed to proceed with installing twrp and vendor.img. When it came time to push (adp push) cm13 to /sdcard, adp gave me this error: "adp: error: connect failed: no devices/emulators found". "fastboot devices" shows that the phone is connected and the recover mode screen shows fastboot mode. (Sorry, can't post a link to the install instructions because this is my first post).
I can get into twrp but trying to boot the phone normally does not work. I get an error saying that the device is corrupted, and then the boot hangs at the weird google animated logo. The screen never shuts off and the animated logo just keeps going around and around.
I can't do a hard reset because I keep ending up at twrp when I try to follow the hard reset instructions.
What should me next steps be?
Thanks.
Click to expand...
Click to collapse
As usual, a good night's sleep and some googling helped me find a solution:
I followed the instructions from Google itself to completely reinstall the factory image: developers[dot]google[dot]com/android/nexus/images
Lack of hyperactive kids (the root cause of my initial mistake) allowed me to carefully follow the instructions.
Now my phone is back in its original state - except that I chose the factory image that matches the version of Cyanogenmod I want to install - and I can start the process over.

GT-P5110: does not reboot automatically after fresh firmware updated...

Hello,
After a tentative firmware update I now get the 'Firmware upgrade encountered an issue' error message when I boot my Samsung tab P5110. I have tried to connect via Kies but Kies does not recognize it. I have then tried various versions of Odin (3.7, 3.9, 3.10) associated to several .tar.md5 that I found on the sammobile and other websites as well. Some {Odin, .md5} couples do lead to a successfull flashing result. The strange thing is that at the end of the succesfull flashing result Odin says 'Restart' or 'Reboot' but my P5110 never reboots, even after 15min. If I then reboot it manually (Volume Down +Power) I get again the 'Firmware upgrade encountered an issue' error message.
I am really lost and do not know what very minimal 'thing' I could flash to get pass this error message...
Thanks for your precious help
Christophe

Help to Samsung SM-J260M

Yeah, well.
I was trying to root my phone (SM-J260M) when the following error appeared on my device:
"An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
But on the Smart Switch I don't get anything to recover or reinstall. You only see what the image shows. I followed the steps of other users but I didn't show what to them, that option to reinstall. So, I downloaded the firmware from Frija and I have come across that it does not install the software. Clarification: you cannot enter the download mode or the recovery mode, it has remained on that screen. If I turn it off and try to enter one of the other modes, it simply shows the screen error I mentioned again. Do you have any solution?

Stuck in locked bootloader download mode

Hey all, hope everyone is having a great day (I'm not),
I own a SM-T510 Samsung Galaxy Tab A 10.1 WiFi.
It all started when I tried to flash Nexus and it worked partially, but I didn't gain access to my internal storage for some reason, so I reverted back to stock rom.
Then for some reason part of the nexus rom was still there, but I was afraid of damaging my device further.
For some reason, netflix wasn't working, so I tried to apply a software update to my device using Smart Switch.
The update didn't work and I was caught in a Nexus bootloop. I entered download mode and I tried flashing twrp using odin. I thought it worked until I realised that it wouldn't get past the teamwin screen.
I re-entered download mode and there it gave me an option to factory reset the device while locking the bootloader. This is where I screwed up as I thought what else could possibly happen to my device?
SO I locked my bootloader and whatever I did I couldn't get out of download mode. AND here I screwed up even more. I tried to flash the stock ROM again using odin as a last resort but it just wouldn't complete after 10 minutes, so I closed Odin and restarted my device and here I am, stuck in a screen that says, "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." Now obviously this wouldn't work because my device isn't even listed there. But to note, my device is recognised by Odin and my PC.
Note: I am an absolute noobie at rooting so be easy on me.
Note 2: adb and fastboot doesn't work for me for some reason, my powershell says, "The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again."
Thank you all for any help. I am at my wit's end.

Categories

Resources