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
Related
Hi all,
I recently installed the newest build of Slimbean. I am having a few issues: I am unable to play any media... Music, videos (youtube). My phone app does not work. I cannot receive nor send any calls. And my phone produces no sounds at all.
I tried installing build 7 to see if it was an issue with the build I was using... didn't help.
Internet and wifi work without any problems.
Galaxy S4 i337m
Baseband: I337MUMUAMDL
Version: Slim-4.2.2.build.7-OFFICIAL
Build #: slim_jfltecan-userdebug 4.2.2 JDQ39E eng.blk_jack.20130706.15730 test-keys
Any ideas?
Thanks in advance
Update: Any ROM I install... Phone and sounds do not work.
Talabis said:
Update: Any ROM I install... Phone and sounds do not work.
Click to expand...
Click to collapse
I'd Odin back to stock and see if you still have the issue. If you do it's a hardware issue.
jd1639 said:
I'd Odin back to stock and see if you still have the issue. If you do it's a hardware issue.
Click to expand...
Click to collapse
I did just that... But it's a bit of a story.
I had just fixed another problem I was having yesterday. Was getting stuck at the S4 splash screen right after powering on the phone. The problem was caused by TWRP 2.6 and formatting /data partition. Long story short, I installed CWM and used it to do a full wipe/format of partitions and then was able to install ROMs, restore backups without issue.
So today, since everything was working, I decided to flash a new custom ROM (which I installed) and the MG1 radio. Wasn't having any luck with the radio. Finally, I was able to flash a radio via mobile odin, but then I soft bricked my phone. Got stuck at the S4 splash screen (same issue I had yesterday, but this time, a different cause). So was troubleshooting it all day. Tried to go back to stock, no luck. Tried to restore the stock backup I had, no luck. Only thing I could do was install custom ROMs at this point to get into my phone (i.e. Slimbean, FoxHound, etc...). But, at this point, although I could boot into Android, I had no sound at all and couldn't play video. So after hours of trial and error, I installed CWM again (replacing TWRP 2.5.0.2), did a full wipe/format and tried to install a stock ROM. No luck. Still was hanging at the S4 splash screen. Then I tried to install this ROM again which I had luck with in the past; |ROM| |★VLUAMG1★| |CANADIAN||i337M||STOCK||ROOTED||July.26.13|. But his instructions said to install a wifi fix or fear soft bricking my phone. So I installed the wifi fix, but selected the wrong file (I know, stupid. Done a lot of stupid **** in the past couple days with this phone). Now, after the phone rebooted, I would see the S4 splash screen for a split second, and it would auto load into download (odin) mode. Couldn't get into recovery at all. So then I decided to flash one of the stock ROMs I tried earlier that didn't work, but this time, SUCCESS!!!!! Phone was booting and all sounds worked. I could make/receive phone calls as well... Everything seems to be working fine now. I find it funny that flashing a wifi fix that I shouldn't have seems to have fixed my issue in a sense. Since it allowed me to successfully flash a stock ROM. So I am making a backup of the stock ROM and will decide what I'm going to do from here.
Holy goalie!!! It's been a very vexing couple of days.
Nice that you got it all worked out, I've found out that if your "status" is custom, it will sometimes give you problems when flashing a "stock" rom via odin.
So what I always do when reverting back to the stock rom, I use triangle away to clear the flash count and make my phone back to "Official". If you want the steps to do this, let me know, it's not hard, but there are crucial steps to get this right!
JP
I have scoured the internet to find someone with the same issue as me, and I haven't found enough to fix the issue, so I'm placing a plea for help here. I have installed TWRP 2.6 recovery, and I am trying to flash OmniRom 4.4.2 nightlies. Originially I was trying to flash cyanogenmod 11, but I had this same problem. It appears to be any kit kat rom that causes the problem (I haven't tried flashing stock or any non-kitkat roms, but I was running on rooted stock before I tried to flash CM11). Anyways, When I flash I am wiping dalvik, cached, system, and data. Then flashing the rom, then flashing Paranoid android gapps. It will boot the first time fine. My phone will work just fine afterwards. However, if my battery dies or I restart, I will be unable to boot back into the rom and my phone becomes a soft brick. It will just stay stuck at the galaxy s 4 logo for as long as I leave it on. I have left it on for more than 30 minutes and there are no changes. I can't have my phone being just a dead battery away from being bricked, so I am asking for your help! Anything is much appreciated!
One other side note: I had my phone just lock up on me once in the middle of it running just fine. Afterwards it turned off on its own and tried to restart, but it resulted in the same issue. I don't know if this is related or just a bug in the rom.
schmidty455 said:
I have scoured the internet to find someone with the same issue as me, and I haven't found enough to fix the issue, so I'm placing a plea for help here. I have installed TWRP 2.6 recovery, and I am trying to flash OmniRom 4.4.2 nightlies. Originially I was trying to flash cyanogenmod 11, but I had this same problem. It appears to be any kit kat rom that causes the problem (I haven't tried flashing stock or any non-kitkat roms, but I was running on rooted stock before I tried to flash CM11). Anyways, When I flash I am wiping dalvik, cached, system, and data. Then flashing the rom, then flashing Paranoid android gapps. It will boot the first time fine. My phone will work just fine afterwards. However, if my battery dies or I restart, I will be unable to boot back into the rom and my phone becomes a soft brick. It will just stay stuck at the galaxy s 4 logo for as long as I leave it on. I have left it on for more than 30 minutes and there are no changes. I can't have my phone being just a dead battery away from being bricked, so I am asking for your help! Anything is much appreciated!
One other side note: I had my phone just lock up on me once in the middle of it running just fine. Afterwards it turned off on its own and tried to restart, but it resulted in the same issue. I don't know if this is related or just a bug in the rom.
Click to expand...
Click to collapse
Omni clearly states that it is an alpha, so you mileage may vary considerably.
Sounds kernel related. Have you tried just reflashing the kernel and seeing if it'll boot after that. Or trying a different kernel?
Thanks for the reply! I actually just fixed the problem on my own. I used Odin to flash a newer version of TWRP and then flashed omni, and it looks like everything is working just fine. I read a few people saying that they were having issues flashing kit kat roms with older versions of recovery, so I figured it was worth a shot.
I have been a lurker around here for some time, but never posted. So Howdy!
I am having some troubles with my LG G2. I have loved the phone so far, and has custom TWRP recovery and rooted. Other than that the device was stock with some very minor mods (xPosed framework, etc..
I stupidly forgot that I had TWRP installed, and I chose to take the recent T Mobile OTA. The phone wouldnt boot past recovery despite a factory data reset. I flashed the stock rom (tried both D80110C and D80110G) to no avail. factory data reset again, re root, installed TWRP again, cleared cache and dalvik, and everything was fine EXCEPT the knock on feature doesnt work. Knock on works just fine, but I cannot knock to wake the device. The power button wakes the device just fine.
Anyone have any thoughts?
Also,
I was considering flashing a rom, like Gummy rom. I don't really have any hypothesis behind this, as I have already flashed the stock rom kdz twice now.
sailoholic1234 said:
Also,
I was considering flashing a rom, like Gummy rom. I don't really have any hypothesis behind this, as I have already flashed the stock rom kdz twice now.
Click to expand...
Click to collapse
Hey, is your knock on issue resolved? also try CloudyG3 rom, its realy smooth.
Hi I need desperate help
two days ago I went from CM11 to S4I9505 Google Play Edition ROM 5.0.1 and everything was running perfectly. Today I used an app known as "ROM Installer" to flash TWRP easily which it did but I couldnt go back to normal menus and it kept on booting back to Recovery. So I wiped everything and installed the same ROM as it is in my External SD. It was successful but it still would boot to recovery and nothing would work. So I thought my option was to unroot the phone. I used the XDA Unroot/Unbrick guide and used an Android 5.0. Lollipop firmware to flash the stock firmware (second time every using Odin, the first was disastrous and I hated it). I flashed the official stock and it is running but cannot activate WiFi what so ever. It just refuses to toggle. So I reflashed the stock firmware again and it still doesn't work. I was thinking of somehow downgrading to KitKat, use CM Installer which is how I initially rooted the phone and revert to a CWM backup that I made before I flashed the S4 GPE ROM and start over. However I tried using that CM Installer and since im on Lollipop it would refuse to work and I really wanna get back to how everything was before :'( I really dont know what to do (No warranty or anything on this S4) All I can do is make calls and texts. Please help!
fixed!
I've fixed it! Its all back on stock with the all that bloatware and useless features only problem now is whether there is a way to deleted this thread
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!