Develop Bugs

flash gone wrong? twrp to cwm?

Hey everyone, I had just flashed cyanogen 10 kang with twrp and everything was fine until I decided to try and get the nexus s 4g modem which I had failed at every time before that. I would flash the rom, then gapps, Then the nexus modem patch before the shadow kernel. This time I flashed the shadow kernel before the nexus modem patch and it had apparentally powered itself off (I had left the room) so I tried to boot back into twrp, but it popped up with cwm 5.0 something instead. And the only backups I have are for twrp. . After I looked around in it for a little I tried flashing the rom and gapps again, booted up fine except I don't believe I had any signal. At all.
I tried to find something that would put twrp back onto my phone but haven't had any luck. And for some reason when I booted back into recovery it had changed to cwm 6.0 something. I don't know what to make of any of it. Right now I'm on cm9 snapshot beta 4 i think. I thought it was the one with twrp already in it so I thought I could try and restore my stuff.
Anyone have a remedy for this? I'd really appreciate it. Thank you in advance for your time.

swiftstrike763 said:
Hey everyone, I had just flashed cyanogen 10 kang with twrp and everything was fine until I decided to try and get the nexus s 4g modem which I had failed at every time before that. I would flash the rom, then gapps, Then the nexus modem patch before the shadow kernel. This time I flashed the shadow kernel before the nexus modem patch and it had apparentally powered itself off (I had left the room) so I tried to boot back into twrp, but it popped up with cwm 5.0 something instead. And the only backups I have are for twrp. . After I looked around in it for a little I tried flashing the rom and gapps again, booted up fine except I don't believe I had any signal. At all.
I tried to find something that would put twrp back onto my phone but haven't had any luck. And for some reason when I booted back into recovery it had changed to cwm 6.0 something. I don't know what to make of any of it. Right now I'm on cm9 snapshot beta 4 i think. I thought it was the one with twrp already in it so I thought I could try and restore my stuff.
Anyone have a remedy for this? I'd really appreciate it. Thank you in advance for your time.
Click to expand...
Click to collapse
You have to flash nyankernel or just the twrp zip. And next time when you flash from twrp, you need to pick inject twrp if you don't want cwm.
Sent from my SPH-D700 using Tapatalk 2

not trying to "thread-jack" - but I have a really similar problem (minus the twrp - which i'm not familiar with). Throughout my update to the crespo modem, during the mtd/bml check the phone would reboot into cwm - and I noticed that just like OP, the cwm would change to some 5.0version (not the usual 6 version)....
Here's what I have:
I was on CM Kang 7/30 with shadow kernel
I updated to CM Kang 8/08 (no problems)
I flashed the http://darkierawr.com/Android/Users/...atchcm7AIO.zip and I kept on getting Status 7 errors... I downloaded it a few times with the same result.
Then I saw someone say they flashed the kernel first and then the modem update... so I flashed the http://dl.dropbox.com/u/820341/Shadow-2_CM10_MdmCrp.zip (successful) and then tried flashing the modem update. Got stuck in a boot loop - so I did a battery pull.
Did a cold boot (pressing power) and now the phone "doesn't have a modem" no radio, no signal etc...
Tried it all over again - mounted system - formatted system - flashed 8/08 kang, gapps, then the modem update, and kernel.
my phone boots but no signal. is there a odin version of the modem that I can flash? or does anyone have any ideas?!?!?!
thanks!!

altimuh said:
not trying to "thread-jack" - but I have a really similar problem (minus the twrp - which i'm not familiar with). Throughout my update to the crespo modem, during the mtd/bml check the phone would reboot into cwm - and I noticed that just like OP, the cwm would change to some 5.0version (not the usual 6 version)....
Here's what I have:
I was on CM Kang 7/30 with shadow kernel
I updated to CM Kang 8/08 (no problems)
I flashed the http://darkierawr.com/Android/Users/...atchcm7AIO.zip and I kept on getting Status 7 errors... I downloaded it a few times with the same result.
Then I saw someone say they flashed the kernel first and then the modem update... so I flashed the http://dl.dropbox.com/u/820341/Shadow-2_CM10_MdmCrp.zip (successful) and then tried flashing the modem update. Got stuck in a boot loop - so I did a battery pull.
Did a cold boot (pressing power) and now the phone "doesn't have a modem" no radio, no signal etc...
Tried it all over again - mounted system - formatted system - flashed 8/08 kang, gapps, then the modem update, and kernel.
my phone boots but no signal. is there a odin version of the modem that I can flash? or does anyone have any ideas?!?!?!
thanks!!
Click to expand...
Click to collapse
Try http://marcusant.com/android/epic/modem.bin
Sent from my SPH-D700 using Tapatalk 2

Random reboots with custom ROMs

Hi All
I've been having such trouble flashing custom ROMs on my Samsung Galaxy Tab Pro 10.1 WiFi SM-T520. I was sucessfully able to flash TWRP 2.8.7 via odin on the device. However, I've tried several ROMs (CM11, 12, 12.1, Unofficial Liquidsmooth) each with their own issues but whichever is able to be flashed always ends up with random startup reboots. I cannot for the life of me figure out why or what is the reason. If I flash back to stock Samsung firmware, everything is fine, works perfectly but no custom firmware.
CM12.1 out right hangs during install in TWRP. The only way I was able to install it is via Cyanogen Recovery which I flashed via odin then attempted to install the rom but even still ends up in random reboots during first bootup and a few times during optimizing apps.
Just a note, I have been doing full wipes (cache, data, system) prior to flashing the ROMs. I don't know what else to do. CM12.1 works really great and smooth but cannot use it because of these random reboots. Can anyone shed some light so I can have a successful flash?
ALSO, I would like to note one suspicion I have and that is my tablet came preloaded with KOT49H.T520UEUAOD1 (T520UEUAOD1_T520XARAOD1_XAR) Samsung Firmware Build. I wonder if perhaps something with this latest build shipped is causing my troubles but am not sure.
Thanks in advanced!

Try booting back to recovery immediatly after new rom flash and perform factory reset and it ahould fix it in most cases.
Sent from my LG-D800 using XDA Free mobile app

I tried the factory reset suggestion but unfortunately did not make a difference.

Are you restoring any backups after flashing? I have been having the same issue, since flashing back to stock. I didn't like stock so I went back to CWM 12.1, which worked flawlessly before. now having random reboots, and the longer I leave it on my system, it's takes longer and longer to wake each time. The only difference between now and the first time I flashed, is, this time I restored a backup! I to, wipe before and after flashing!

Mossey said:
Are you restoring any backups after flashing? I have been having the same issue, since flashing back to stock. I didn't like stock so I went back to CWM 12.1, which worked flawlessly before. now having random reboots, and the longer I leave it on my system, it's takes longer and longer to wake each time. The only difference between now and the first time I flashed, is, this time I restored a backup! I to, wipe before and after flashing!
Click to expand...
Click to collapse
No backup/restores involved for me. Are you still experiencing this issue with CM12.1 or was restoring the backup the problem in your situation?
I am wondering if perhaps the bootloader version that is based off of the latest official stock ROM that was released in April/May 2015 has something to do with my issues. Is there anyone that was on the latest stock Samsung ROM that has been able to successfully flash a custom ROM and use it in a stable way (short of minor CM bugs)?

[SOLVED]TWRP bootloop, CM12.1 bootloop, Not sure what to do here..

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.

Phone bricks when trying to flash new ROM?!

I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Does anyone know what the problem could be?

I would suggest you clean flash OOS first before going to Freedom.
I think RR is based on Lineage OS while Freedom is based on stock OOS.
Envoyé de mon iPhone en utilisant Tapatalk

Wrong forum.

danecr7 said:
I would suggest you clean flash OOS first before going to Freedom.
I think RR is based on Lineage OS while Freedom is based on stock OOS.
Envoyé de mon iPhone en utilisant Tapatalk
Click to expand...
Click to collapse
RR is based on CM. I'm just scared to flash OOS in case it goes wrong because stock OOS will overwrite TWRP with its stock recovery and then I'll be screwed because I'll have no way to restore from a backup if it goes wrong

RazorBlade123 said:
Wrong forum.
Click to expand...
Click to collapse
Yeah I thought it seemed a little out of place but I don't know where to post it? Is there a general questions forum?

evilkitty69 said:
RR is based on CM. I'm just scared to flash OOS in case it goes wrong because stock OOS will overwrite TWRP with its stock recovery and then I'll be screwed because I'll have no way to restore from a backup if it goes wrong
Click to expand...
Click to collapse
I don't think that there is a risk in flashing stock OOS. But if the custom recovery is overwritten then flash it back, your backup files are stored in your internal memory and unless you wipe it you are safe.

danecr7 said:
I don't think that there is a risk in flashing stock OOS. But if the custom recovery is overwritten then flash it back, your backup files are stored in your internal memory and unless you wipe it you are safe.
Click to expand...
Click to collapse
Even when I tried flashing other CM based ROMs, including ones I'd flashed before, it failed, only flashing RR actually worked. I don't know why this is the case but I'm not sure flashing OOS without knowing what the issue is, is the solution because if I lose TWRP there's no telling whether I'll be able to flash it back in fastboot if the phone isn't working properly

evilkitty69 said:
Even when I tried flashing other CM based ROMs, including ones I'd flashed before, it failed, only flashing RR actually worked. I don't know why this is the case but I'm not sure flashing OOS without knowing what the issue is, is the solution because if I lose TWRP there's no telling whether I'll be able to flash it back in fastboot if the phone isn't working properly
Click to expand...
Click to collapse
I once flashed RR based on android 7.1.1 and because I did not like it very much I wanted to go back to Freedom but at that time it was based on android 7.0.1 thus I was unable to boot. Maybe you are facing the same issue. But in my case I hardbricked my device and used the unbricking tool from OP3 forum.
If you download the latest OOS zip file you can flash it through TWRP and you won't lose you custom recovery.

danecr7 said:
I once flashed RR based on android 7.1.1 and because I did not like it very much I wanted to go back to Freedom but at that time it was based on android 7.0.1 thus I was unable to boot. Maybe you are facing the same issue. But in my case I hardbricked my device and used the unbricking tool from OP3 forum.
If you download the latest OOS zip file you can flash it through TWRP and you won't lose you custom recovery.
Click to expand...
Click to collapse
All of the ROMs I tried with were android 6.0.1, I'm avoiding touching android 7 because I'm not a fan
The strange thing is that in TWRP under "mount", system is unchecked and it won't stay checked when I reboot or try to flash something and then the flash fails. Strangely however, I can flash RR afresh and it will work but nothing else works
Therefore I don't think OOS would work either

Stuck on TWRP after trying to update to 9.0

Hey there,
I've been using an old beta of OmniROM Oreo for months now, but wanted to try the 9.0 ROMs that are out there. I followed the instructions in both the Lineage and Omni threads and updated to the TWRP that's needed, then flashed the chiron firmware that's needed, then wiped all and formatted data, then installed the ROM. When I went to flash the rom, TWRP told me that my filesystem was read only and suggested I leave it that way for security. I said OK, everything installed fine, but when it restarts it fails to boot the OS and then reboots into recovery (TWRP). I have tried flashing the firmware, different ROMs, etc., but not getting anywhere.
I'm assuming this is related to leaving the filesystem read-only, but not really sure.
Anyone know what I did wrong? And how to fix it?
Thanks