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?
Related
this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.
chirantan.f said:
this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.
Click to expand...
Click to collapse
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)
i would also like to note here that i tried installing AOSP based ROMs also, and AOKP didnt work, got stuck at nexus like boot animation forever, but when i tried installing CM10.1.2 (which is what i was running when i tried to get back to TW based ROM) it worked perfectly, so for now i am back to CM, but i would really get back to flashing different ROMs and trying them out. just makes me wonder if CM is the reason i am not able to install anything else, just a thought...
has anybody else tried going to any other ROMs from CM 10.1.2?
your help is appreciated!
pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
Click to expand...
Click to collapse
thanks for your reply, but i have tried doing that, i also wipe data and system along with cache and dalvik before installing any new ROM.
pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)
Click to expand...
Click to collapse
i have latest recovery , TWRP 2.6.0.0 and i have given more than an hour to boot up and still nothing. i have been flashing ROMs like an addict since i got this phone last year, but when CM 10.1 stable was released i stayed on it till today, but now i cannot install any other ROM, i can odin to stock 4.1.1 ROM or install cm 10.1.2 which i did just now, but no other ROM, either TW based on AOSP based is working...which is very weird for me.
Were you able to fix this issue at all? I am facing the same issue, in my case, the phone was encrypted on stock TW. I roooted and put in CM 10.1.2 and now when I try installing Dandroid, the install itself would work but I am struck at the "type password to unlock the screen". If I reflash CM10.1.2, I can login fine. Any pointers?
Hello together,
first of all, i have an european E975. At the beginning with this phone everything was all right, nearly every custom rom and stock Roms (through KDZ flashing) went fine (except the mentioned bugs). But after flashing an stock kitkat based miui Rom where my sim card wasnt recognized (never had this before with this phone) no Rom runs good after KDZ flashing back to 10f. This means nearly every Rom (even Stock) has now problems i havent got before with the SAME zip packages and versions.
For Example, any cm based Rom have a wakeup issues, so the softkeys turns on but the screen turns black, or screen lightens up but freezes. 4.2.2 MIUI has now additional problems that nearly every app freeze and force closes and on 4.4 stock it takes often 10 seconds to wake the device up. And I am using the same zip files i used before, which ran great and without these problems before flashing the kitkat based miui. And i used the same procedure to flash an custom rom as before, this means kdz flashing 10f, wiped data, framaroot, busybox, freegee with mako twrp, wipe data, system and cache in recovery, flash Rom, flash gapps, wipe data again and boot.
So my question is, could there be other partitions that could be overwritten or damaged that cause the problems? Or is there another way than KDZ flashing to get rid of unnecessary files?
Thank you in advance
I have updated my rom to CM12 a while ago and after that my recovery (TWRP) stopped working. Yesterday, I finaly decided to fix it, so I flashed CWM (it worked!) and I tried to update my rom to the latest CM 12 nightly build. When it booted into the OS, I get a bunch of error for Text-to-speed, Google play service, UI System, etc. I tried to wipe, reflash, reinstall gapps... same thing. Then, I tried to only install the os : Wipe, install the rom, boot still get the errors.
Anyone, has any idea on how to fix this?
I have a SGH-M919 (Samsung galaxy S4 - T-Mobile), I downloaded the JFLTETMO version of CM12.
You should start over.
Factory reset, reflash a stable version of cm12 and stay away from the nightlies.
Nightlies are experimental changes that are put out so you can try them on your phone. They don't always go well and your left with a phone that doesn't work.
If you need your phone to function properly you may consider stable CM11 or a stock rom.
Pp.
PanchoPlanet said:
You should start over.
Factory reset, reflash a stable version of cm12 and stay away from the nightlies.
Nightlies are experimental changes that are put out so you can try them on your phone. They don't always go well and your left with a phone that doesn't work.
If you need your phone to function properly you may consider stable CM11 or a stock rom.
Pp.
Click to expand...
Click to collapse
Thanks for the reply, I downloaded a Stable build of CM11 and flashed it, but my phone kept rebooting in Recovery. I noticed that the sdcard/ folder is empty like if nothing was installed in the phone. I decided to flash TWRP. And when i flash the rom I get an error:
"E: Unable to open zip file."
"Error flashing /sdcard/rom3.zip"
Edit : Forget about the error I think the file was corrupted during transfer. Still getting the boot into recovery thing.
Try removing your SDCARD from the phone.
Turn phone off, remove SD card and start over. This may allow you to flash without errors.
Afterwards if successful tryout phone and then reinsert SD card.
Pp.
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!
Hello,
Since I got my XT1635-02 in April I have tried to use LineageOS and/ or AOKP. The problem is, when I flash either, I get an endless bootloop.
When I got the phone I:
Unlocked the bootloader
Flashed TWRP - the latest 3.1.1-0
Flashed Lineage ROM
I don't use Gapps - or I'd rather not - but at this stage I have flashed the Pico package
Then flash su-addon.
I've tried different combinations; only flashing LineageOS/AOKP but got the same result.
Stock images work fine for me. I even got to the point where I had to write a little bash script to flash all of the components in the correct order for the RETUS Nougat image.
Last month, by some fluke I got LineageOS to boot. However, I have no idea what I did differently, it just seemed to work that one time. However, I have been living off of that install for about 3 weeks and the OTAs even worked perfectly.
Today I got bored and decided to flash AOKP.
Booted in to TWRP
Wiped Dalvik, Sys, Data, Cache
Flash AOKP
Reboot
Bootloop.
Is there something wrong with my phone or is there something wrong with my process?
Any suggestions welcome. Thank you.
I remember​ that problem with Razr. Some custom roms were booting fine, some bootlooping.
The first workaround was to flash working one then without reboot flash desired one.
Later we figured out that wiping/formating partitions was the problem. Bootlooping rom couldn't read the file system. Solution was to not wipe or to wipe to the correct file system.
Sent from my XT1635-02 using Tapatalk
I think you may be on to something because I had flashed LineageOS after flashing the stock Nougat image. Still, would like a surefire way to just run a ROM. I've never had this issue on any other device.
I had it on Razr and just started to happen after one CM nightly build. Turned out that devs changed FS.