I was rocking an old S.E.A.L. ROM for a couple years until it started becoming unbearable due to apps crashing and random reboots. So I downloaded a couple new ROMs to try, along with a new kernal, and put them on the sdcard storage.
I did a factory reset wipe, and tried flashing with TWRP. Couldn't seem to run the install properly and kept getting corrupt file errors.
So I used ODIN to update TWRP to 3.0.0. I tried all kinds of flashing again with the same errors. So I re-downloaded the zips and moved them to ExternalSD. The flashing process now seems to go smoother, but the problem is that it doesn't seem to actually write anything to the device. However, I did flash the latest SuperSU zip and that seemed to create a folder, etc..
I tried using ODIN again to re-flash the recovery (to try TWRP 2.8.7) and that seems to fail now. So it appears I'm stuck with TWRP 3.0.0. I can boot into Recovery and Download modes no problem.
I've tried just about every approach to ressurect this tablet with a fresh ROM and nothing is working. My head is approaching the explosion point.
I'd appreciate any advice!
Thanks!
Related
I'm very confused as to what happened, and feel like I'm only making things worse so decided to come here. I've been rooted for about 2 months now after using Unrevoked Forever, and until last week everything was fine.
Using Rom Manager I attempted to flash Salvage Mod coming from Cyanogen 6.1.2. After wiping Data/Cache, when going to open the Zip Clockwork told me that the Rom did not exist in my SD card?
I redownloaded and tried again several times with no luck. I tried downloading other ROMS through my computer and putting them directly on my card and now I'm getting an error saying the Zip files are "(bad)"
Flashed RA Recovery through Rom Manager, the same errors, and now flashing back to Clockwork won't work. Any ideas what the problem maybe? Any solutions would be greatly appreciated
Have you tried booting to recovery directly and flashing a rom? I personally use CWM 2.6 and prefer to do all the work myself through recovery instead of hoping RomManager gets it right.
Yes I've tried booting into Recovery myself, keep getting the error that the zip. is bad
I'm new to rooting phones and have run into an issue with my SGH-T989. First let me say that I did several days worth of reading and investigation to make sure that I was comfortable moving forward. I rooted the phone without any issues using ODIN3 v1.85 and CWM SuperSU v0.87.
After that, I decided I'd like to try installing a ROM - Beanstalk-4.4.2_R1-v205-Linaro-20131216-hercules.zip. Again, I followed very specific instructions but ran into issues first with the version of JB radio I had on the phone (T989UVLI1).
When the BeanStalk ROM install failed, I tried using CWM Recovery to restore my stock ROM but that also failed on an MD5 hash mismatch. I suspect that's probably because I modified the folder name after I ran the backup- again, following some online instructions but wasn't really thinking when I did it.
I rebooted the phone after the failed stock restore, it went back to a semi-stock state like it was a new phone set up however I was having issues with entering recovery mode through CWM and TitaniumBackup was acting a bit flaky as well.
I was finally able to get the phone to enter CWM Recovery mode by holding down the power and volume up/down buttons and then proceeded to flash the radio to T989UVMC6 and flashed the ROM- however I forgot to wipe the flash before I installed Beanstalk.
Now the phone boots into Beanstalk, but none of the GAPPS work and I can't get into Play Store to try and install anything to fix the problem.
I'm also starting to suspect an issue with the rootware since I'm getting messages to that effect through TB and CWM ROM Manager won't launch without immediately force closing.
Anyone have any suggestions to offer?
Thanks in advance!
Quick update - I got GAPPS installed and so far things seem stable. Still not able to restore my stock ROM though, so I may be stuck with BeanStalk 4.4.2 for now.
So all of a sudden I'm unable to install new ROMs. I've tried several different ones and the same happens for each of them.
It freezes here:
Installing '/sdcard/*ROM name*.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
It just stops here and says "Flashing file 1 of 1" at the bottom of the screen. The progress bar doesn't move. I let it sit there for 30 minutes and nothing. I've updated to the most recent version of TWRP, I've tried mounting the system partition before starting the install and I've tried several different ROMs. I always end up having to hold down the power button for a while to shut the phone down, then restore my backup. I'm currently using cm-11-20141112-SNAPSHOT-M12-m7vzw.zip ROM and openrecovery-twrp-2.8.4.0-m7wlv.img Recovery
I don't think this is related, but the reason I'm trying to flash a new ROM is because my GPS stopped working after installing the one I'm currently on.
JGress said:
So all of a sudden I'm unable to install new ROMs. I've tried several different ones and the same happens for each of them.
It freezes here:
Installing '/sdcard/*ROM name*.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
It just stops here and says "Flashing file 1 of 1" at the bottom of the screen. The progress bar doesn't move. I let it sit there for 30 minutes and nothing. I've updated to the most recent version of TWRP, I've tried mounting the system partition before starting the install and I've tried several different ROMs. I always end up having to hold down the power button for a while to shut the phone down, then restore my backup. I'm currently using cm-11-20141112-SNAPSHOT-M12-m7vzw.zip ROM and openrecovery-twrp-2.8.4.0-m7wlv.img Recovery
I don't think this is related, but the reason I'm trying to flash a new ROM is because my GPS stopped working after installing the one I'm currently on.
Click to expand...
Click to collapse
The GPS failure seems to be a common issue when using GPE and AOSP roms. I've had it myself in the case of both CM and GPE. One way to help avoid it is to turn GPS on in a sense rom, get a good GPS lock, then wipe and flash your non-sense rom. As for your problem flashing a ROM, have you tried any other versions of TWRP? If you are unable to get into a ROM to flashify, I would try rolling back to older versions using fastboot. Personally I have not tried flashing a full ROM with 2.8.4 yet, but 2.8.3 worked fine for me so maybe you can start by rolling back to it. I don't know if any TWRP settings might be preserved when overwriting a version of it with a different one, but you could also try flashing the stock one before flashing TWRP again. If that doesn't work, your last resort would probably be to wipe using the stock recovery or flash the factory image found here:
http://forum.xda-developers.com/ver...nt/ruu-vzw-kitkat4-4-3-sense-6-s-off-t2867643
Remember it wipes everything.
I had a similar problem last year. I had inadvertently installed a twrp recovery meant for my Thunderbolt onto my m7. I opened the zip and read the build.prop file and saw I had the wrong recovery. Just sounds like a mistake I've made.
Sent from my ADR6400L using Tapatalk
Do anyone know what to do here. I got a note 2 from my aunt for fixing her S6, I figured I would use this as an extra device to play around with but I absolutely HATE TouchWiz so I wanted to put CM12.1 on it, now I've done this probably thousands of times before, this phone is screwed, I can't figure out why. Even on my old Note 2 it worked, can't get this working, no idea why.
My aunt has done all the OTA updates since she bought it brand new so it was running 4.2.2 DNF4, I did a system restore to get rid of all her stuff, once it booted to the welcome screen to set it up I rebooted into download mode, used odin to flash the latest twrp, all good, wiped the phone, flash the latest cm12.1 nightly and latest opengapps, wipe dalvik, reboot, reboots back into twrp, nothing I can do, I tried this a few times with different builds and even different roms, nothing works, twrp is screwed and will not let me leave once it boots, I have to pull the battery.
So I flashed back to stock touchwiz 4.4.2, rebooted back to download, flashed CMR, figured it must work better since it's right on the download page for CM12.1, wipe it, flash the files, reboot, stuck in a boot loop at the cyanogenmod face, sits there for hours, nothing happens.
Tried the exact process using cwm and philz, nothing works, I literally can't flash anything AOSP, I've tried other roms and only stock touchwiz will boot past the boot screen, and stock touchwiz has no problem running if I run CMR, CWM, or Philz, but TWRP doesn't work on anything, it will not let me leave if I boot into recovery unless I pull the battery and let it boot normal.
Any ideas at all? I'm getting completely fed up with this phone and I'm going to throw it in the garbage if I can't figure this out, I've wasted the same amount of time that if I spent this much time at work, I could have bought a used Nexus 5 by now lol
I used DN3, U HAVE TO WIPE 3X WITH OLDER TWRP, FLASH PHILZ, dont WIPE , THEN INSTALL ROM.ITS ALL REALLY A PAIN.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
How old are we talking for TWRP? As in a different version of 2.8.x or like 2.7.x or maybe even 2.6.x?
EDIT:
I followed your instructions and that actually worked.. I used the latest TWRP for 2.7 which was 2.7.1, I'm going to play with this a little more tomorrow and see what the latest version of twrp is that I can use without getting stuck in a boot loop, thanks a lot for that info.
The only issue I've run into now is I got Error 12 while trying to flash GAPPS so currently there are no GAPPS installed.
Glad you're running. GAPPS very touchy on some roms, Go to ROM thread for that stuff.
I'm just running regular untouched CM12.1 nightlies, any GAPPS should work but the recovery is telling me it's out of date and can't use it stbin or something like that?
However, I found out that once CM12.1 is installed, and before it's set up, I can reboot back into download, flash with odin TWRP 2.8.5 which is the newest I've found that works. and it will let me flash the latest GAPPS, the phone still boots back to the setup/welcome screen, and then I can set it all up as if everything was fine.
It's quite the work around but at least I was able to get it all working.
I also tested this again using DNF4 and it also works using this twrp to wipe and philz to flash method.
Thanks again.
I tried flashing an old, alpha, version of sailfish on my phone and since then it's been bootlooping. I can access the recovery and install CM11 but after booting it restarts, every 1-2 minutes. Flashing some other roms gives me bootloops (First boot takes >1 minute, the phone resets).
I've already backed up all my data and wiped internal and external storage, but flashing gives me the same problems.
What can I do? I have the latest TWRP installed.
EDIT: Some ROMs seem to work. I just flashed PAC LP MR1 20151011 and it worked. Most other roms don't work. Do I need to update firmware? I don't understand why this is happening
try to flash the latest fastboot rom to put the phone to stock settings and then try again with other roms
Have you tried flashing firmware files from #3 in cm 11/12.1/13 thread?