So, my phone ran out of power last night. I charged it up, but upon removing the charger, and booting into my main ROM (Stock-based, .200 or .232 I believe. AndroPlus' Advanced Stock Kernel with MultiROM support) the device bootlooped on the purple Xperia animation.
I left it on charge overnight, booting, and when I woke up, it was still on the same animation. I have MultiROM installed, through TWRP. I flashed a ROM (CM-based, 5.1.1 with the included kernel), and booted. It worked! But, if the Files app was opened, it would display nothing, internal or external SD. Sideloading ES File Explorer yielded similar results. Thinking it was a problem with the ROM, I flashed CarbonROM (CM-based too, I believe. Same version.) and similar things happened. However, TWRP can access both internal and my SD Card. I believe that no hardware damage has occurred.
So. Is it possible to fix my main ROM, or back up the data from it and migrate it to a new stock-based ROM? Thanks.
EDIT: I should mention that under available storage, both ROMs listed the correct amount of storage space, as did TWRP.
nothing broken in hardware, something is wrong with multiROM. Try to reflash kernel. If it won't work flash ftf rom via flashtool
Related
I tried flashing Ken's GB ROM today and for some reason it would just load the AT&T screen then restart. I flashed the zips through CWM, what might I have done wrong?
which recovery did you use? did you wipe? and try to re-download it. you may have gotten a damaged file. it happens. this is why we have MD5 sums
I used rom manager, I wiped after (maybe I should have done it before?), and what's an mds sum?
Sent from my MB860 using XDA App
I just used the new official CWM for Atrix (as opposed to tenfar's custom build) to flash navalynt's CherryBlur1.2 over my old 2.3.4HKTW ROM, which I had modified with navalynt's 1.8 rollup package.
I'm also bootlooping on the Atrix logo (instead of the Motorola logo; I think it was part of the theme included in the update package, and it'd be nice to be able to change it back to the stock somehow). I'd take your advice and try redownloading the .zip of the ROM, but, uh, I don't really know how to access my phone's internal storage without being able to boot it up.
Should I manually try flashing the .img files via fastboot interface, or what? I really picked a bad time to screw with my phone, because I'm expecting a call about a new job...
Obscene Topiary said:
I just used the new official CWM for Atrix (as opposed to tenfar's custom build) to flash navalynt's CherryBlur1.2 over my old 2.3.4HKTW ROM, which I had modified with navalynt's 1.8 rollup package.
I'm also bootlooping on the Atrix logo (instead of the Motorola logo; I think it was part of the theme included in the update package, and it'd be nice to be able to change it back to the stock somehow). I'd take your advice and try redownloading the .zip of the ROM, but, uh, I don't really know how to access my phone's internal storage without being able to boot it up.
Should I manually try flashing the .img files via fastboot interface, or what? I really picked a bad time to screw with my phone, because I'm expecting a call about a new job...
Click to expand...
Click to collapse
Yea, if you didn't make a nandroid backup, you need to flash the image files of your previous rom
Sent from my MB860 using XDA App
Well, this is very strange. I restored the backup I had made, although I got an error from CWM about being unable to wipe /data... nonetheless it booted properly. I loaded a new download of the .zip, flashed it in CWM with no apparent errors, and now instead of bootlooping on the custom Atrix animation, it's bootlooping on the Motorola "dual core technology" screen (not the actual bootloader screen with "unlocked" in the corner, but after that). I'm really confounded by all of this.
Forum is full of similar threads.
Rom Manager doesn't successfully wipe. You need to run a fastboot -w or reinstall tenfar's CWM and wipe, then reinstall your ROM. This will resolve your bootloop.
EDIT: You're seeing the same problem...bootlooping. The ROM's just have different boot animations: Atrix logo vs. Default Moto.
quicklyspent said:
Forum is full of similar threads.
Rom Manager doesn't successfully wipe. You need to run a fastboot -w or reinstall tenfar's CWM and wipe, then reinstall your ROM. This will resolve your bootloop.
EDIT: You're seeing the same problem...bootlooping. The ROM's just have different boot animations: Atrix logo vs. Default Moto.
Click to expand...
Click to collapse
Yes, I just used fastboot to reflash the stock HKTW images, and of course it's fine now. I'd just like to be able to get CherryBlur to work properly.
Edit: Got it. The .zip installed properly using tenfar's CWM. Ironically enough, tenfar's custom implementation of CWM works better than ROM Manager's, although obnoxiously it's unable to mount the phone's internal SD storage, so an external SD card must be used for installing .zips. ROM Manager's CWM can mount the internal storage, but has other issues. Lol, so convoluted.
Obscene Topiary said:
Yes, I just used fastboot to reflash the stock HKTW images, and of course it's fine now. I'd just like to be able to get CherryBlur to work properly.
Edit: Got it. The .zip installed properly using tenfar's CWM. Ironically enough, tenfar's custom implementation of CWM works better than ROM Manager's, although obnoxiously it's unable to mount the phone's internal SD storage, so an external SD card must be used for installing .zips. ROM Manager's CWM can mount the internal storage, but has other issues. Lol, so convoluted.
Click to expand...
Click to collapse
It's just a matter of time before rom managers cwm works properly
Sent from my MB860 using XDA App
I am unlocked, rooted, on the latest TWRP. And can't flash any roms. Every time i do a wipe and go to flash it immediately tell me failed. However I can flash my recoveries. TWRP doen't see my internal storage (sdcard). But does see my external and I still can't flash from there. I am stuck on energize rom 4.1.1 How do I get past it? Mind you I am sitting on a mil base in Iraq net is slow but I still try.
Hoping someone here can help me fix this problem without having to RUU and start all over...
I'm S-On with 2.09 HBOOT.
I had been running MeanBean for the last 6 months or so, but decided to finally give an AOKP ROM a try because I wanted to check out HALO. First, I did a Nandroid backup of MeanBean using TWRP. Then I downloaded the latest DirtyUnicorns build, placed it in on my SD card and flashed through TWRP (2.3.1), inlcuding the attached GApps and the CM10.2 data fix. It wouldn't boot at first, and I realized that my old kernel for MeanBean was Sense-based, so wasn't compatible with AOKP. I extracted the boot.img file from the ROM and flashed using fastboot. After that I was able to boot up and was up and running with Dirty Unicorns on Mazda's supplied kernel.
DU is pretty awesome and there is so much to do in the ROM, plus HALO is awesome. I wish that was incorporated into every ROM. But my battery life the first couple of days left much to be desired. Even using Kernel Tuner to underclock with screen off and Llama to turn stuff off when I didn't need it, I was approaching 30% by lunchtime. So in an effort to try and fix this, I tried to flash the latest Haunted HC kernel (DU thread says people have flashed this and it runs) through Flash Image GUI since I am S-On. Unfortunately, the phone went into a boot loop after this and wouldn't get past the HTC screen. When I got home I reflashed the DU kernel through Fastboot, but then my WiFi wasn't functional.
After trying to flash a few times and it not working (WiFi still broken), I decided to just go back to MeanBean using the Nandroid. Used TWRP to do this, but then the phone wouldn't boot past the HTC screen after this. Was stuck at my girlfriend's and didn't have fastboot available, so I reflashed DU off of my SD card and it booted up and runs, but now I can't access my internal storage. This means I can't use Swiftkey and the Gallery app isn't functional either. When I try to mount internal storage in TWRP to reformat it, it just says internal storage cannot be mounted. Does anybody know how to fix this??? Everything I could find on here says that I should be able to mount using TWRP at least, but I can't even get that to work.
TLDR - Been flashing ROM's/kernels and now can't mount internal storage.
FIXED - Was able to use Rumrunner to obtain S-Off (had attempted while on MeanBean and would not work), then updated recovery to the latest TWRP and used the Advanced Wipe feature to reformat the internal storage. After that, I just reflashed DU and was up and running. Only issue I had was phone lost connectivity to Sprint, so I had to go back to MeanBean just to update my profile.
Hello there,
Well, to preface what has led me into the situation that I am in right now, I had installed SS in the hope of creating a virtual ram disk and installing a custom rom within it. Where I messed up is that, despite me having the virtual rom created, I flashed a ROM zip over the stock android rom and not on the virtual rom slot, thus locking me out of my phone. I had done a standard factory wipe before installing the new rom and (unless I am incorrect) have wiped out the usb debugging functionality I had previously enabled as a result. When starting my phone, I am still able to access the custom recovery that SS has installed (I545 Safestrap 3.75 (TWRP v2.7.10)). However, from there I attempt to boot the phone into system, I get an error notice to the effect of "There is software Verizon doesn't supprot please take this to your nearest Verizon store, etc, etc." With a notice at the top saying kernel failed - and at that point if I attempt to start the phone by pulling out battery and restarting, it negates the option to log into SS/TWRP recovery and leads me to that verizon incompatibility screen all over again.
This is where it get interesting though
(I would use link functionality to post a Heimdall screenshot but I couldn't remember my old xda account info and it prohibits users w/ less than 10 posts from posthing links)
If I attempt to reflash the MDK kernel through Heimdall, despite it saying that it failed in the log, my phone reboots and it once again brings me to the SS splash screen at the ability and I able to get back into the SS/TWRP recovery yet again. Very weird.
I have been primarily following instructions from this site: droidview's "how-to-install-latest-official-firmware-on-samsung-galaxy-s4-all-models" (which you can find easily via those terms in google without me posting link)
I have been using the original .pit file that I have pulled from my own phone from heimdall myself (before I locked myself out of stock rom compeltely) but do have a PIT file copy from the website where I have been referencing before.
I have yet to try to flash a zip file of a 4.4.2 verizon ROM via the SS/TWRP recovery because I don't have any SD card readers in my computer and had previously put the custom firmware I had wished to install on my sd card via mounting my phones SD card through the stock ROM to my pc before I messed up overwriting it. The functionality for SS mounting sd card via the recovery itself seems to be broken so that isn't an option. However, I could borrow a phone from someone else and mount my SD card through their phone and access it from my PC that way.
All attempts of reflashing via ODIN on my windows partition have failed as well. ODIN recognizes my device but, following the instuctions from the instructions I referenced earlier, have resulted in it displaying a "FAIL" message almost immediately.
Thanks for taking the time to read this much and I'd appreciate any help I can get.
Hi there,
Not sure what happened - I'm using my Tab S3 (SM-T820) for ages in the same (stable) configuration - rooted Stock, no changes/installations for months.
This morning it was in Odin/Download mode and I cannot boot into system.
I can get into recovery (TWRP), but I cannot boot into system from there either, it always returns to Odin (tried wiping Cache/Dalvik, didn't help).
For now my only idea is to let it completely discharge, charge again and give it another try.
No buttons appear to be stuck.
Any ideas or suggestions, eg sth I could check in TWRP to see what's going on?
(hopefully nothing wrong with the system partition).
Note - I'm only familiar with the typical TWRP functions needed to install custom firmware, haven't used it for much else. Obviously would prefer not to destroy my (stable) setup and spent a full day re-installing everything
Thanks a lot for your help everyone!
@Whoooo? Backup whatever possible with TWRP onto external storage (SD or OTG).
Check if file manager can access download/DCIM folders and save them as well.
Although the charging thing might help I wouldn't set my hopes to high.
Probably somethings wrong with system or boot partitions or any file needed by them.
I'm afraid you will have to reflash stock via Odin, root again and try if restoring TWRP saved Data works.
That would reduce setting up time.
bmwdroid said:
@Whoooo? Backup whatever possible with TWRP onto external storage (SD or OTG).
Check if file manager can access download/DCIM folders and save them as well.
Although the charging thing might help I wouldn't set my hopes to high.
Probably somethings wrong with system or boot partitions or any file needed by them.
I'm afraid you will have to reflash stock via Odin, root again and try if restoring TWRP saved Data works.
That would reduce setting up time.
Click to expand...
Click to collapse
Hi there,
Thanks a lot for your reply - yes, I will try that once the complete discharge is finished.
Reflashing stock - could cause this any troubles as it's already unlocked/rooted?
Or is there a chance dirty flashing the Tweaked Stock ROM could work, too?
Tablet was still on the original Stock it came with, but rooted with magisk and manually debloated...
Thanks again!
I think Odin won't care about unlocked bootloader.
But might be necessary to unlock again.
Dirty flashing afaik only works with TWRP so only flashing of zip or img files possible.
Except you sideload although Idk if that's possible on Samsungs.
Dirty flashing of a before the problem arose made backup might work.
Did you debloat while already installed or externally?
What file format does it have?
My T825 uses the debloated ROM by rorymc628 which can be flashed with TWRP as it's a zip file.
bmwdroid said:
I think Odin won't care about unlocked bootloader.
But might be necessary to unlock again.
Dirty flashing afaik only works with TWRP so only flashing of zip or img files possible.
Except you sideload although Idk if that's possible on Samsungs.
Dirty flashing of a before the problem arose made backup might work.
Did you debloat while already installed or externally?
What file format does it have?
My T825 uses the debloated ROM by rorymc628 which can be flashed with TWRP as it's a zip file.
Click to expand...
Click to collapse
Hi there and thanks again -
Took me a while to try everything but finally it's working again.
Complete battery drain didn't help, but dirty flashing did - once I got the correct version.
Basically made a nandroid backup, then flashed the tweaked rom over my existing one, starting with newer versions down to older ones.
So, flash, reboot - didn't work, restore nandroid (all), flash slightly older rom....
Till it started booting with v2.0 (probably matching my existing rom close enough).
Had to reflash Magisk as the 2.0 Rom included didn't match my Magisk Manager, but now my Tab S3 is working again!