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.
Related
Hey guys,
Every time I try to install the "Monster_2.3.2_4.5.153_updater_Rooted.zip" ROM from Droid Life the install aborts with an error message and I have nothing left to do but to remove the battery and reinsert it. When I do that however, I get to the boot loader with an error message and I have to revert to the stock SBF and re-root my phone, re-bootstrap recovery, boot in recovery, and try again - I'm feeling lucky. I have done this about seven or eight times, nine as we speak, and so far with absolutely no success. I would really like to know if I am doing something wrong here, I have installed other ROMs with success such as Fission and Liberty.
The last few lines of error message in the installer were as follows:
...
Unmounting Systen ...
updatinig radio image ...
assert failed: motorola.update_cdma_bp("/tmp/rdl.bin", "/tmp/bp.img")
E:Error in /sdcard/Monster_2.3.2_Rooted.zip
(Status 7)
Installation aborted.
---
The Device being used is a Droid 2 Global with the stock SBF running.
And that is all that I get, this problem has repeated itself many times and I have tried installing the above ROM while having another version and ROM installed both with no success. Any help is greatly appreciated.
Have you tried to apply that monster.zip file from the Bootstrap Recovery app & choose the option to choose the zipfile?
Do you have it in the root of the /sdcard directory?
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?
Hey all,
I'm not a total noob, but I do this so infrequently that I can't commit it to memory. Would really appreciate some help here.
I followed the official LineageOS Guide for Herolte, over here.
I had done this previously on my Nexus 7 so I was fairly confident.
Everything worked well, I got TWRP installed using Heimdall from Linux, and successfully pushed the latest LineageOS and open_Gapps images to the phone.
Rebooted into TWRP, and followed the recommendation to wipe System, Cache and data partitions. This failed with red text stating that ti was unable to mount data.
I googled some, and found a suggestion to reformat the partitions, first to a different file system and then back to their original file systems again. I tried formatting /data to exFat, and it took forever, eventually erroring out with an error message. After this I can't get into TWRP anymore. When I try the phone boots to the TWRP startup screen, and just freezes there.
I have tried reflashing TWRP using Heimdall and this does nothing. Flash succeeds, nut still freezes at TWRP splash screen.
I googled some more and found a suggestion to flash stock Samsung firmware, and then try again, this time formatting data system and cache without trying to first wipe them. Problem is I can't successfully flash stock firmware.
I tried using this method in Heimdall, but it complains "Local and device PIT files don't match and repartition wasn't specified!" and fails.
I've also tried booting into Windows and using Odin, but it never works. The screen turns grey, and no progress indicators ever start. I assumed this was because I had the incorrect drivers for the phone, and tried using zadiag.exe to replace them, but the driver install fails.
I'd greatly appreciate any help. I can't seem to force the phone to shut off, it just keeps rebooting and getting stuck on either the TWRP spash screen or on the download mode screen. I know this is solveable, but unless I figure it out fast, I'm worried I am going to burn in the screen.
Any suggestions appreciated!
Never mind. I must just have had a bad stock image.
I downloaded a different one, and retried heimdall and it flashed properly.
I am now able to re-flash and boot into TWRP again.
Hopefully I won't have the same problem again when I try to wipe the partitions...
Alright,
So I solved this issue by (once I reflashed stock, and then reflashed TWRP again) formatting the data partition twice, first to ext3, and then back to ext4. This looks to have cleared the encryption issues that were causing thsi problem ,and allowed everything to continue working as expected.
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.
A while ago I had a ROM running but switched back to OOS due to battery drain. Time passed and I wanted to give it another go and tried installing another ROM, after getting the recommended variant of TWRP running I tried doing the usual, wiping then installing, but as soon as I tried flashing the ROM it kept giving me this log:
Code:
Flashing A/B zip to inactive slot: A
Step 1/2
Error applying update: 26 (ErrorCode :: kDownloadMetadataSignatureMismatch)
Updater process ended with ERROR: 1
To flash additional zips, please reboot recovery to switch to the updated slot.
Error installing zip file '/sdcard/<insert filename>.zip'
etc
I thought maybe it was because the ROM had failed to download properly, so I tried a different ROM and downloaded the other one again, but it still gave me the same error. I tried several things like formatting the storage because I saw a youtube video doing that, but although my phone boots normally if I try to download anything it fails. Not sure why this is happening. I still can't flash any ROM.
If partitions have been corrupt
I think you have hetter to flash latest "oos fastboot"
then restart from a "kind new" phone
anyway,
tipically with .zip file, also a .md5 or .md5sum file Is published
if you start checking It, you will not run in this kind of problems
WayneKosi said:
A while ago I had a ROM running but switched back to OOS due to battery drain. Time passed and I wanted to give it another go and tried installing another ROM, after getting the recommended variant of TWRP running I tried doing the usual, wiping then installing, but as soon as I tried flashing the ROM it kept giving me this log:
Code:
Flashing A/B zip to inactive slot: A
Step 1/2
Error applying update: 26 (ErrorCode :: kDownloadMetadataSignatureMismatch)
Updater process ended with ERROR: 1
To flash additional zips, please reboot recovery to switch to the updated slot.
Error installing zip file '/sdcard/<insert filename>.zip'
etc
I thought maybe it was because the ROM had failed to download properly, so I tried a different ROM and downloaded the other one again, but it still gave me the same error. I tried several things like formatting the storage because I saw a youtube video doing that, but although my phone boots normally if I try to download anything it fails. Not sure why this is happening. I still can't flash any ROM.
Click to expand...
Click to collapse
Long shot but did you figure this issue out? Im running into the same issue with my Oneplus 7 Pro