Update 6/23/20: Solved! Had to replace the logic board.
I didn't install any new apps, no system updates and woke up to find a very warm S7 (SM-G930V) stuck in a boot loop. This is not rooted, but running the latest G930U firmware on a G930V device. No issues for years until today. Recovery mode does not work and I can't get it to boot into safe mode. I got it into download mode successfully and was able to flash the latest G930U firmware with a "pass" on ODIN. But the boot loop persists and it seems to get to random points in the boot then restarts. Right now it showing the "no command" but then reboots, other times it doesn't make it past the logo screen on startup. Odd that this happened out of nowhere seeing I didn't initiate anything different with the software on the device. Since I have access to ODIN is there anything I should try to get a successful boot? Checking a different box maybe? Seeing this is aging I'm hoping it's not a motherboard issue...
Update: After repeated attempts I can occasionally get into recovery. Tried wipe/reset and clearing partition cache but no changes.
Update #2: When trying to flash back to stock I get a "pass" in Odin, and during the install on the phone it stops the install process and brings me to the android recovery screen. Here's what it says:
-- Installing package...
Finding update package...
Opening update package...
E: Unable to open '/cache/recovery/sec_csc.zip': No such file or directory
E: Failed to map file
Installation aborted. #2
Update #3: I was able to use the PIT file and flash again but with repartition and NAND erase and the boot was successful for once. But after a minute it immediately shutdown and went back to boot loop. I'm thinking either battery or motherboard issue at this point. Thoughts?
Battery
It's not the battery, I just swapped that to confirm. I'll try replacing the logic board now I guess.
Solved!
Replacing the logic board did the trick.
Related
I attempted to flash the MOAR rom 8.0.0, and I first flashed the ML1 radio beforehand, then I reset like normal after flashing a new rom.
Waited 15 minutes at the Samsung Galaxy S3 logo and did a battery pull, second boot got me into the rom which then had a system UI error and reset, it was then perpetually stuck on the logo, no amount of waiting would get past it.
Then i attempted to restore my old rom from backup, but while going into TWRP this mysterious message appeared that never happened before:
Updating partition details...
E:error opening '/data/media/0/Android/obb'
E:error: I/O error
E:error opening '/data/media/0/Android/obb'
E:error: I/O error
I can't wipe anything as somehow everything on my phone has become read-only, and installing a new rom has no effect, even rooted ADB can't push files to the internal memory, any ideas on how to fix?
Update:
Nevermind, fixed the problem by using TWRP to do a complete format, phone now works fine, I didn't find anyone with the same problem as me using a search, so leaving this thread might be a good idea for future searches.
Hello Guys!
Recently i received my used Motorola Moto G. Phone was nice, I was using it like every teenager, instagram snapchat etc. But last night i wanted to install rom on phone. Saw thread about installing everything, root rom etc. with 1 program. I tought it will be nice, so i downloaded it, run, and there is a problem. It was command line tool, everything gone right, there was messeage about clicking any button to continue, I did it and then my phone restarted, but there was like normal 5.0.2 android not 5.1 what was saying guy who wrote thread about that program. So i thought that i will do everything step by step, unlocked bootloader, installed recovery and when i first time opened recovery from bootloader menu it had problem with mounting data partition. I was trying to install firmware roms, but it had problems with downgrading bootloader. Downloaded 5.0.2 firmware .xml.zip file, it gone ok, i mean there wasn't a problem with motoboot.img, and at every single command there was only okay, there wasn't failed, just had 2 problems on phone screen, it was saying "hab check failed for boot" and "hab check failed for recovery". After typing every single command to fastboot and restarting phone always phone was stucked on boot screen, i mean on 4.4 it was stuck on messeage about unlocking bootloader, on 5.0.2 it was stucked on that 4 colors orbs flying around the screen. Then i was trying to open my stock recovery, but it was always broken, opened android with warning sign on it. When i was installing custom recovery that had problems with mounting /command /log /last_log /last_install, and when i was trying to mount data it couldn't mount it, I was trying to format /data and /data/media, it was always going ok and then i could mount data partition, but my phone was still stuck on boot screen. I was trying to install custom recovery again but it had same problem, just opened android with warning sign. And there is a question, what can I do to make my telephone working.
I'm sorry for mistakes, but my english is not the best
Try reading this thread here and see if that helps.
I have a TV110 (Amlogic S805, 1gb/8gb) Android TV Box. I was trying to replace the stock ROM with Openelec v5.0.8 from Kerber. The update went fine until it rebooted to launch Openelec then it hung at the Openelec logo for over an hour. I thought the box was hung so I removed power and rebooted. It hung again in the same place so I decided to use the reset button to launch recovery. I must have cycled power too quickly because it would only show the boot logo and would go no further. Something was seriously wrong with the box.
I created a bootup SD card with TWRP recovery on it. I booted up into TWRP 2.8.6 without any issues but could not restore any of the partitions. TWRP was getting errors trying to mount all the partitions. I figured I could go back to stock (I have a NAND backup). When I try to wipe or restore it fails because the partitions are not mounted. I tried to install the old firmware using the install from TWRP and I get "Error executing updater binary in zip".
At this point I am stumped. What do I do next?? How do I get my box bootable again?? Can I somehow re-create the partitions??
Any help would be appreciated.
Hello! I installed BlissPop on my tablet before getting the new one from the callback program. This worked fine for several months, until suddenly the tablet decided not to boot.
The current situation:
The tablet boots onto the Nvidia logo, stays there for about 3 mins, then starts booting BlissPop. The boot is then stuck at the BlissPop animated loading screen. (It does not freeze the tablet or anything like that)
The tablet is not bricked (I think). I do not get the bricked error when checking on serial number. I dont remember which version of BlissPop i flashed over half a year ago.
What I have tried:
1) Flash a new custom ROM through Recovery, installing from zip through adb. I get an error while installing from zip:
- mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/UDA at /data: Invalid argument.
- unmount of /data failed; no such volume.
- Patching system image unconditionally
Also, I cannot mount /data or /cache from CWM. Is my partition table messed up?
2) Flash to stock recovery image, through fastboot.
These steps always end up in the same way, nothing has happened during the flashing or installation. The device is still in the same state.
3) I tried installing another recovery type (now using CWM v.6.0.5.0), but I always end up with the old one.
What seems to be the common result on whatever I try, is that nothing happens. I even tried erasing all the data from the tablet, but nothing changes. Still boots into BlissPop and is stuck there. It seems like I cannot write anything to the tablet. Recovery mode (CWM) is also VERY slow, and it takes about 3 mins to get into CWM from fastboot bootloader screen.
Does anyone have any idea what I'm doing wrong, or have any tips for new things to try out?
Hello,
My phone(Samsung galaxy s8) just had a crash and is stuck on the blue screen with "Installing update". After several seconds the screen goes away and boots straight into the recovery mode.
The log that i see in the recovery is :
Fail to open recovery_cause(No such file or directory)
Failed to mount /efs
Unknown volume for path /odm
dm-verity verification failed
I tried to install the stock firmware (I cant link to the webpage but im 100% sure its the correct one) but it wont boot and goes to the "Installing update" again and after that to the recovery.
I tried installing twrp but it wont install due a FRP lock. i read that you should wipe your data and factory reset. Also tried that but again no succes.
Can someone please help me.
Thanks in advance
nickglas said:
Hello,
My phone(Samsung galaxy s8) just had a crash and is stuck on the blue screen with "Installing update". After several seconds the screen goes away and boots straight into the recovery mode.
The log that i see in the recovery is :
Fail to open recovery_cause(No such file or directory)
Failed to mount /efs
Unknown volume for path /odm
dm-verity verification failed
I tried to install the stock firmware (I cant link to the webpage but im 100% sure its the correct one) but it wont boot and goes to the "Installing update" again and after that to the recovery.
I tried installing twrp but it wont install due a FRP lock. i read that you should wipe your data and factory reset. Also tried that but again no succes.
Can someone please help me.
Thanks in advance
Click to expand...
Click to collapse
I'm going to take a guess here, you had the device rooted and then you tried to apply an OTA stock update while the device was rooted? Tyically, stock OTA updates can't be applied to devices that have been rooted because the updates require the device to have an unmodified system partition(no root) and they require stock recovery instead of custom recovery. There are "some" devices that can apply stock updates while rooted, but those are few and far between.
If that is what you did, you need to do some searching for repairing failed OTA updates on rooted devices.
Sent from my SM-S767VL using Tapatalk