I'm not exactly sure but i went through a bunch of threads and ended up going back to stock from LOS and back to L21B432 marshmallow
Not sure how to get back to L22B636 marshmallow, do i just flash the rom?
Related
Hey guys. I am not sure what is going on. I am not sure if its a hardware issue on my phone, or if its a bug on NC2 radio or what. Anyway, back when NC2 first came out, and I didn't do all the reading right I had upgraded it. Well I didn't like the fact you couldn't create ROM slots yet in SafeStrap with NC2. I had flashed my factory ROM slot with one of the ROMS that were available at the time and at least twice a day I would have to reboot the phone because it would just start running VERY VERY slow.
I ended up downgrading back to MJE and figured I would wait until SafeStrap had working ROM slots again.
Well here I am a few months later, SafeStap now supports rom slots...so I upgrade back to NC2, update to the latest safestrap and flash a rom...same issue....Does it on the factory nc2 rom as well....What gives?
Not sure what noob mistake I made here, but i can only flash CM based roms.
I unlocked the bootloader and loaded TWRP no problem. I've been running CM for months but wanted to try something else. I went with Resurrection Remix and realized i had no GPS. So i tried AICP, no GPS, Then Mokee, no GPS, then back to CM13 which worked before... No GPS! I saw threads saying to load rom based on stock and gps lock then reflash, so i tried but nothing else will boot!
g900v
Using twrp 3.0.2-2
No Boot.
Note5 Port
BS FREE
vzw stock something.. i already deleted this one and can't remember which it was now.
They all just bootloop.
What am i missing? Or if there is a gps fix i don't really care about loading non cm based roms, as thats likely what i'll go with in the end, but i need gps.
Flash a close to stock rom such as a rooted touchwiz rom in twrp
[email protected] said:
Flash a close to stock rom such as a rooted touchwiz rom in twrp
Click to expand...
Click to collapse
Thanks i tried a ton of stock based roms and nothing would load.
I tried to go back to stock on PD1 and that didnt work either. even after flashing kernel and stock rom through odin, it would lock on the verizon logo. no amount of factory resets or thread recommends helped. I ended up going to PB1 stock using odin and that fired right up after a pb1 kernel flash.
So i'm back at pb1 stock now, which is borderline unusable without root if nothing more than the constant dust cover notifications and update notifications that i can't seem to stop.
At least gps and everything works 100%. guess ill be following the pb1 root guide at some point soon. or maybe ill just do the ota to pd1, at least in 6.0 you can disable notifications on apps which would solve some of my issues..
Ok glad to hear you got it figured out
Sent from my SM-G900V using Tapatalk
I actually just ran into the same thing but I'd like to try and figure it out so I don't have to odin after updating ROMs. Hopefully my TWRP log attached. (Originally it was 9mb so I trimmed it down.)
This is my first time reading recovery logs but it looks like it's having an issue writing to some areas. I read on the net that someone had a similar issue due to encryption. I have never knowingly enabled encryption but i do use fingerprint lock. I tried removing that completely and testing again but get the same errors in the log. TWRP doesn't display any errors at time of flashing a TW ROM that I noticed.
Running latest TWRP 3.0.2.2 (i think that's it) using CM13. Tried multiple TW ROMs (and downloading) but other custom ROMs work fine.
Any thoughts?
Sent from my SM-G900V using Tapatalk
Sorry, I only now realized my logs never attached. Anyway, I was able to get it straightened out although I never determined the root cause.
I completely started over from scratch, odin to stock, root, unlock bootloader. I did continue to have issues flashing ROMs (including CM now) but finally resolved that by failing back to TWRP 3.0.0. Now I can flash Cam and TW ROMs again. I made a TW nandroid so if the GPS goes out again I should be able to easily do the CM->TW->CM trick.
I may have been firmware or partition corruption that CM just didn't care about but there may also have been related to TWRP > 3.0.0.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Hi there
I have recently picked up my old S4 since my OPO screen broke. I was annoyed with the buggy CM 12 nightly it was running and tried installing the newest CM 13 nightly. It gave me no signal and I decided to try to revert to stock, following the guide Unroot/Unbrick, Flash official stock firmware on S4. Applying the I9505XXUAMDE_I9505OXXAMD8_NEE 4.2.2 stock rom through ODIN was a breeze but after booting i realized it had no sound.
Also placing or receiving calls makes the phone hang, even occasionally reboot, and sometimes a window with "android.phone.. app" or "process system is not answering" appears. For example also not possible to record video.
I did both factory reset and wipe cache in bootloader, but when wiping cache I get the lying down android with red exclamation mark for a few seconds then reboot.
I then tried to reflash above stock rom with repartition (pit file) and the problem remains.
I dont suppose it is a hardware problem since it started after I flashed new rom. It seems like some audio related software issue that I cant seem to get rid of - can anyone help or should I just give up and get another phone?
Thanks in advance, sorry for the long post
Try flashing a newer ROM.
The guide used is pretty old I guess and should be used only as reference.
What was the initial stock ROM your device had?
Pwnycorn said:
Try flashing a newer ROM.
The guide used is pretty old I guess and should be used only as reference.
What was the initial stock ROM your device had?
Click to expand...
Click to collapse
I already tried rerooting and flashing back to both CM 10.2 and newest CM 13 nightly from philz touch recovery. Both with the same problem when placing or receiving a call. But sound was working..
I don't know the exact stock rom the phone came with but seem to recall it was 4.2.2 as I have installed now.
Is there anything else that can be flashed back to original? I read several posts talking about a modem reflash for fixing audio issues but I suppose the stock rom should contain the modem info already..?
I specifically went for the oldest rom, since the guide said that once stock 4.3 is flashed you cant revert due to new bootloader. And I was hoping to revert to being able to use OTA updates since I plan on gifting the phone to an even more tech illiterate than myself.. Is that going to be a problem if I just flash for example the newest 5.0.1 stock rom?
fiedes said:
I already tried rerooting and flashing back to both CM 10.2 and newest CM 13 nightly from philz touch recovery. Both with the same problem when placing or receiving a call. But sound was working..
I don't know the exact stock rom the phone came with but seem to recall it was 4.2.2 as I have installed now.
Is there anything else that can be flashed back to original? I read several posts talking about a modem reflash for fixing audio issues but I suppose the stock rom should contain the modem info already..?
I specifically went for the oldest rom, since the guide said that once stock 4.3 is flashed you cant revert due to new bootloader. And I was hoping to revert to being able to use OTA updates since I plan on gifting the phone to an even more tech illiterate than myself.. Is that going to be a problem if I just flash for example the newest 5.0.1 stock rom?
Click to expand...
Click to collapse
Downgrading causes problems in the first place, that is why it is recommended to flash the same software as it originally had.
As long as your status says "official" in download mode, you should be able to still get updates. Although who knows for how long.
I also recommend using the latest TWRP recovery. PhilZ and CWM are outdated and can cause problems with newer ROMs.
Pwnycorn said:
Downgrading causes problems in the first place, that is why it is recommended to flash the same software as it originally had.
As long as your status says "official" in download mode, you should be able to still get updates. Although who knows for how long.
I also recommend using the latest TWRP recovery. PhilZ and CWM are outdated and can cause problems with newer ROMs.
Click to expand...
Click to collapse
I will try to install TWRP and the newest stock firmware and see what happens. Thanks
Ok, upgraded to latest stock rom and everything works!
No idea what was wrong specifically though.. Thanks for the help!
Hey there so recently I have upgraded to stock nougat but I'm getting tired of the lag I'm getting on it, I'm getting it more so than MM before. I didn't bother with custom firmware before as I could tolerate the lag on MM and I could use android pay.
Now browsing around the forums I have gathered that there is a chance if I downgrade it could brick the phone? Am I stuck with the stock firmware for the moment?
Is there any way that I can improve the phone's performance in the mean time?
(I have cleared the cache, it improved for a few days until it went to the normal lag again)
I downgraded the other day just fine from stock 7.0 to stock 6.0.
gpt.bin and bootloader.bin cannot downgrade once updated to the latest (I just ignored the errors and went ahead). Everything else flashed with no errors.
Once back on MM 6.0 I reflashed Lineage OS 14.1. Wasn't impressed with stock 7.0 like I thought I would be.
Just remember, if you downgrade there is no going back to Nougat, and if you happen to mistakenly update via OTA it is instant hard brick... at least until we can manage to get a full factory firmware image of Nougat.
Honestly, if you are willing to go that far, why not start with a simple factory reset?
Factory reset is a must with this update to 7.0 anyone willing to downgrade vs trying a factory reset needs their head examined.
I was enjoying LOS 12.1 for a while but noticed it started to bug out sometimes. Unfortunately tried to upgrade to 14.1 and couldn't get Netflix working, and still can't after downgrading back to 12.1. Since this device is basically just a Netflix machine it's kind of worthless if I can't get Netflix working, or only in SD.
Is it possible to flash a stock ROM in TWRP and go back that way? And back to LOS if I decide to try it again, or does the stock ROM need stock recovery? I don't want to go through all those steps of unlocking bootloader again, I'm surprised I got it working the first time around, heh.