Database Users

[q] urgent help needed

I tried to flash a rom and it didn't go so well due to the fact it was for Verizon S4 only and I missed that,
anyway I decided to go back to my recovered stock TW rooted Rom and everything was fine until... my WiFi stopped working, just wouldnt turn on then was asking me to reboot my device?
after a bit of searching I found out to just revert back to official stock firmware.. BUT
for some strange reason and for the first time ever, when I reflash the official stock firmware it stays as custom and is all buggy and crashes a lot. could this be because I am flashing an official stock that is less updated than my rooted TW?
someone help me cause it's really starting to aggravate me!
thanks!

When you flash the stock, do a factory reset. Any if it does not work, repeat the procedure (reset/flash/reset). But make sure you have the right stock (I suggest to take it from sammobile). I heard of up to 7 tries before success...
good luck

@JacksonPa93:
Can you check if you actually have this problem (WLAN/Bluetooth doesn't work and random crashes with reboots):
http://forum.xda-developers.com/showpost.php?p=44996177&postcount=16

fixed!
I think I've solved it by what was mentioned about factory reset>flash stock
Took me 5 times to eventually get it working..
thanks guys

Slimbean 4.2.2 Build - media issues

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

radio .84 causing my phone bootloop

I had used cm 10.1 for a year and one day I decided to flash slimbean 4.3 weekly 1.4. So I downloaded bootloader Z20i.zip and radio .84.zip and flashed via TWRP 2.6.3.0 and then wiped everything, flashed rom then gapps. I used the original kernel of rom. Everything seem to be fine and flawless. but one day my phone hanged and rebooted itself stucked at bootanimation. I tried to restart many times and it didnt success. So I decided to download factory image JWR66Y from google and run flash-all.bat via fastboot mode and then flash superSU via TWRP. Yeah..bootloop was gone. I used stock JWR66Y rom and kernel with root for a while and it happened again. One day my phone hanged and rebooted itself stucked at X animation. I tried to Wipe cache, davik, factory reset but it didnot success. So I tried to install cm10.2, PA3.99 (I have had installation zip file in my phone storage.) but it didnot sucess too. So I decided to flash stock Stock 4.2.2 JDQ39 image from google. thanks God my phone resurrected. But I dont want 4.2.2 anymore. I decide to try again with 4.3 stock JWR66Y. It happened bootloop same as above I described again. I have no idea anymore but I tried flash radio.48 via fastboot and finally my phone can use normally. Bootloop was gone away. Now I use Slimbean 4.3 weekly 1.6 original kernel with bootloader z20i and radio .48 without any bootloop.
So I think the problem for me is why radio .84 make my phone got bootloop.
Sent from my Nexus 4 using xda app-developers app

quirell said:
I had used cm 10.1 for a year and one day I decided to flash slimbean 4.3 weekly 1.4. So I downloaded bootloader Z20i.zip and radio .84.zip and flashed via TWRP 2.6.3.0 and then wiped everything, flashed rom then gapps. I used the original kernel of rom. Everything seem to be fine and flawless. but one day my phone hanged and rebooted itself stucked at bootanimation. I tried to restart many times and it didnt success. So I decided to download factory image JWR66Y from google and run flash-all.bat via fastboot mode and then flash superSU via TWRP. Yeah..bootloop was gone. I used stock JWR66Y rom and kernel with root for a while and it happened again. One day my phone hanged and rebooted itself stucked at X animation. I tried to Wipe cache, davik, factory reset but it didnot success. So I tried to install cm10.2, PA3.99 (I have had installation zip file in my phone storage.) but it didnot sucess too. So I decided to flash stock Stock 4.2.2 JDQ39 image from google. thanks God my phone resurrected. But I dont want 4.2.2 anymore. I decide to try again with 4.3 stock JWR66Y. It happened bootloop same as above I described again. I have no idea anymore but I tried flash radio.48 via fastboot and finally my phone can use normally. Bootloop was gone away. Now I use Slimbean 4.3 weekly 1.6 original kernel with bootloader z20i and radio .48 without any bootloop.
So I think the problem for me is why radio .84 make my phone got bootloop.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have the same exact problem! :crying:
Cannot update beyond 4.2.2. I have tried all the things that you seem to have tried but with absolutely no luck. And since there aren't many people with this problem, nobody has come up with a solution. It is extremely frustrating to see everyone else updating to to the latest firmware while we have to make do with the ancient 4.2.2
If anybody can think of anything which might help, please go ahead and share.(Cannot return the phone back to Google as I got it from another country)

Rekursion said:
I have the same exact problem! :crying:
Cannot update beyond 4.2.2. I have tried all the things that you seem to have tried but with absolutely no luck. And since there aren't many people with this problem, nobody has come up with a solution. It is extremely frustrating to see everyone else updating to to the latest firmware while we have to make do with the ancient 4.2.2
If anybody can think of anything which might help, please go ahead and share.(Cannot return the phone back to Google as I got it from another country)
Click to expand...
Click to collapse
Hi,
I just fixed a Nexus 4 with broken screen and fastboot flashed the latest 4.4.2 official ROM but I was stuck in bootloop on the 4 circles.
Then I flashed the 4.2.2 version and everything worked until I accepted the the 4.3 update (official OTA) and the phone was bootlooping again.
Then I found your posts and downgraded the radio .84 to .48 and android 4.3 finally booted successfully.
BUT, when trying to upgrade to 4.4 (from 4.3 with official OTA), I'm stuck again! And downgrading radio .97 to .48 does not work anymore...
I've found nothing like a software fix until now. People facing the same issues are mostly getting some replacement devices. Given that I replaced the screen myself, I'm not certain that they would give me a new one.
Any feedback from someone having the same issue?

neoantho said:
Hi,
I just fixed a Nexus 4 with broken screen and fastboot flashed the latest 4.4.2 official ROM but I was stuck in bootloop on the 4 circles.
Then I flashed the 4.2.2 version and everything worked until I accepted the the 4.3 update (official OTA) and the phone was bootlooping again.
Then I found your posts and downgraded the radio .84 to .48 and android 4.3 finally booted successfully.
BUT, when trying to upgrade to 4.4 (from 4.3 with official OTA), I'm stuck again! And downgrading radio .97 to .48 does not work anymore...
I've found nothing like a software fix until now. People facing the same issues are mostly getting some replacement devices. Given that I replaced the screen myself, I'm not certain that they would give me a new one.
Any feedback from someone having the same issue?
Click to expand...
Click to collapse
Yes.., I am joining your club. I have a same problem. I flashed 4.4 & 4.4.2 .., almost all sources and ended with four circle boot loop. Then flashed 4.2.2 and it was success. Did you people managed to flash Kit Kat ? Please anyone help us.

Please try these links...dont know whether it helps...I sold my phone., cant try..
http://forum.xda-developers.com/showthread.php?t=2529450
http://forum.xda-developers.com/showthread.php?t=2347060
Hope it helps someone.

richie16171 said:
Yes.., I am joining your club. I have a same problem. I flashed 4.4 & 4.4.2 .., almost all sources and ended with four circle boot loop. Then flashed 4.2.2 and it was success. Did you people managed to flash Kit Kat ? Please anyone help us.
Click to expand...
Click to collapse
richie16171 said:
Please try these links...dont know whether it helps...I sold my phone., cant try..
http://forum.xda-developers.com/showthread.php?t=2529450
http://forum.xda-developers.com/showthread.php?t=2347060
Hope it helps someone.
Click to expand...
Click to collapse
Hi, yes I finally found out that my proximity sensor was only disconnected (I forgot to reconnect it properly after the screen replacement). Then I managed to update my phone.
Found answers on this thread : http://forum.xda-developers.com/showpost.php?p=49141665&postcount=75
Sorry that you had to sell it...

neoantho said:
Hi, yes I finally found out that my proximity sensor was only disconnected (I forgot to reconnect it properly after the screen replacement). Then I managed to update my phone.
Found answers on this thread : http://forum.xda-developers.com/showpost.php?p=49141665&postcount=75
Sorry that you had to sell it...
Click to expand...
Click to collapse
You mean to say.,,you could flash 4.3 and your only problem to update kit kat.., because of the proximity sensor?

richie16171 said:
You mean to say.,,you could flash 4.3 and your only problem to update kit kat.., because of the proximity sensor?
Click to expand...
Click to collapse
Well, I meant I could get 4.3 to work after downgrading the radio file (baseband) to its previous version, otherwise I was stuck in bootloop in 4.3 already.
But I couldn't do the same operation after flashing 4.4 : even downgrading the radio to a previous version didn't get 4.4 to work.
Once I reconnected the proximity sensor, I could use any radio and was able to update from 4.2 to 4.3 and 4.4 or directly flashing the latest.
You can use the Androsensors app to see if your light and proximity sensors are working properly, the displayed values should change all the time. If they are not changing or if there is no value displayed, it means that your sensors are not working properly

No GPS, now can only boot cm based roms?

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

S5 reboot issues

Hello, i will try to be as elaborate as I can cause I know you guys here are really knowledgeable when it comes to smartphones. So, here are the issues I am currently experiencing with my G900F phone. Just a background, everything in my phone is stock (rom, recovery, kernel) no changes done yet. It currently runs MM with a security patch of February 2017. As of now, I can't boot into the phone.
1. . I was able to successfully root it with CF auto root.
2. I started experiencing random restarts. I tried obtaining the last kmsg however it does not exist.
3. I tried flashing a new ROM thinking maybe there is some rare bug in the stock rom i currently have. I flashed TWRP via Odin, to be able to flash a new ROM. Odin successfully flashed the recovery however when i proceed to install a new ROM through TWRP the phone gets stuck in a bootloop. I do not experience this in the stock recovery
4. I was able to restore the phone through Smart Switch device intialisation. However, with everything stock I still experience the random reboots.
Bottomline: Is there anyway I can fix this on the software side (e.g. flash/update this or that)? And if not, do you think this is a hardware problem? Worth mentioning it's got a yellow screen bug but if i press hard on the back of the phone it disappears. Also, I can boot into stock recovery and download mode without any problems.
Thanks and sorry for the long post really need your insights.

Sorry you are having issues. I apologize if I missed this, but have you tried downloading the official firmware for your device from sammobile or similar sites, then flash that through Odin?