So I was using the BeastMod ROM for a while and decided to go back and do a recovery and use the stock ROM for a while. I got everything all going back to normal with the stock ROM and got a notification about the T-Mobile Wi-Fi calling update that was available. I downloaded the update and then proceeded to install the update. When the phone reboots it pops to the Android and Triangle screen and does nothing.
Any ideas what to do to get this installed?
CStites said:
So I was using the BeastMod ROM for a while and decided to go back and do a recovery and use the stock ROM for a while. I got everything all going back to normal with the stock ROM and got a notification about the T-Mobile Wi-Fi calling update that was available. I downloaded the update and then proceeded to install the update. When the phone reboots it pops to the Android and Triangle screen and does nothing.
Any ideas what to do to get this installed?
Click to expand...
Click to collapse
You have the stock recovery installed?
You'll probably lose root by installing this update. Just so you know.
I installed the stock recovery, went through the set up of the phone like it was brand new and got a prompt to download. Downloaded, and went through install only to come up with the triangle screen upon reboot of phone. I have to pull battery and restart phone.
I realize that it is possible that losing Root is there. I am just having issues with the operation of the phone and want to run stock. I don't mind sense, my only complaint and only initial want for a new ROM was to get rid of the bloatware.
I have not followed up with the ROM and their development in the last two months or so, so do not where there are and the stability of them. I want something that isn't going to take me all day to install on my phone by trying to figure out how to install it and flashing of kernals and other things. I'd prefer to be able to download to and SD card and install the zip through recovery and that be it. Not sure if that is possible.
CStites said:
I installed the stock recovery, went through the set up of the phone like it was brand new and got a prompt to download. Downloaded, and went through install only to come up with the triangle screen upon reboot of phone. I have to pull battery and restart phone.
I realize that it is possible that losing Root is there. I am just having issues with the operation of the phone and want to run stock. I don't mind sense, my only complaint and only initial want for a new ROM was to get rid of the bloatware.
I have not followed up with the ROM and their development in the last two months or so, so do not where there are and the stability of them. I want something that isn't going to take me all day to install on my phone by trying to figure out how to install it and flashing of kernals and other things. I'd prefer to be able to download to and SD card and install the zip through recovery and that be it. Not sure if that is possible.
Click to expand...
Click to collapse
After you flashed CWM recovery, you are very much can flash Rom and theme from recovery by downloading onto your sdcard - as you so wished - with the exception of Faux's kernal
'Til now, we only have 2 kernel: Stock and Faux's and very much all the Roms are based on stock kernel, so, if you referred to avoid the hassle of using your PC - then stay with stock. You'll only need to flash it once and after that, either upgrading or changing a new rom (stock kernel based) you won't have to flash it again .
Exceptions are:
Beside one or two Roms that featured Faux's kernel (can't recalled exactly but very few - read the first post of your would-be Rom), other than that you will have to pay attention to Xboarder latest Rom - the BulletProof. It's latest version (2.2.0) feature Faux's kernel whereas older version based on stock, so, if you flash older BulletProof Version (2.1.0 and backward) you are worry-free to switches from many Roms without being near your PC to flashing kernel.
I'm strongly encouraged you to go ahead and try some Rom, they are very stable and fast. Battery hog is the thing of the past IMHO
Related
ok so i wouldnt say im a noob but im not as advanced as some of yous. last night i flashed a leaked ics onto my phone and loved it with one exception. i couldnt figure out how to root it. all my apps are backed up on titanium backup and i didnt want to have to get all of them manually. so i flashed back to stock using odin with a file i used back when that crappy update came out. i rooted it with super one click and and then went to put on a prerooted ics... when in recovery mode now i get this message
cant access to '/system/csc/att/system/'
i try putting on cwm and siyah and i keep getting authentication errors and the installation aborts. also recovery mode wont read my external sd card now. when the phone is booted up it works fine except i tried to do the factory ota update and it keeps failing. i tried reflashing back to stock again and did the update unrooted and it still failed.
i know you guys hate hate when people ask without researching so i did SOME forum browsing and found nothing. sorry i dont really have time to look too extensively. i just want to know how to fix it. i appreciate any help i can get
Joeyjr25 said:
ok so i wouldnt say im a noob but im not as advanced as some of yous. last night i flashed a leaked ics onto my phone and loved it with one exception. i couldnt figure out how to root it. all my apps are backed up on titanium backup and i didnt want to have to get all of them manually. so i flashed back to stock using odin with a file i used back when that crappy update came out. i rooted it with super one click and and then went to put on a prerooted ics... when in recovery mode now i get this message
cant access to '/system/csc/att/system/'
i try putting on cwm and siyah and i keep getting authentication errors and the installation aborts. also recovery mode wont read my external sd card now. when the phone is booted up it works fine except i tried to do the factory ota update and it keeps failing. i tried reflashing back to stock again and did the update unrooted and it still failed.
i know you guys hate hate when people ask without researching so i did SOME forum browsing and found nothing. sorry i dont really have time to look too extensively. i just want to know how to fix it. i appreciate any help i can get
Click to expand...
Click to collapse
Start with getting back to stock using this guide. Check for ICS bootloaders too, you probably flashed them and you have to get stock ones back (careful, flashing bootloaders can cause hardbricking). Once you're back to stock and rooted, you shouldn't need to ever use PC Odin again.
Then use this guide for rooting/flashing.
One other note: when you tried to install CWM, it sounds like you loaded an update.zip onto your phone then tried to install it using stock recovery. Stock recovery won't let you install unsigned update.zips, which is why that method for getting CWM on your phone will never work (hence the authentication error and installation abort). For our phone, CWM is only included in custom kernels, that's the only way to get it on there, and don't even think about updating or changing it via other means. Just flash a custom kernel, it'll include CWM, use it until you want to switch kernels.
Hit my thanks button, I was really nice this time. And post in Q/A next time as well.
EDIT: Skip the second guide if all you want is stock. You should be able to update OTA after following the first guide. Though even if stock is what you want, I highly recommend flashing a custom GB kernel because a) they're more stable and faster and b) you'll have CWM in case you need it.
You started off mentioning about "leak ics" which I have absolutely zero experience.
My suggestion:
1. Try to get it back to stock. Make sure it works correctly.
2. If hasn't rooted yet, do so.
3. Getting CMW into the device by flashing custom kernel.
4. From there, install any ICS ROM you want.
But I'm a bit (really) confused about a lot of things regarding this process. I've been reading for a week now and barely getting anywhere.
So first, a little history.
I'm running a stock vibrant, Froyo.UVKB5, 2.6.32.9 kernel, never been rooted.
Now, one of the main reasons for my upgrade is the loss of wifi connectivity. For some reason I can no longer connect to most ISP's or WIFI hotspots, especially my own.
Now, here's the kicker; I don't have a data package on my service so I am dependent on wifi only. Now that I can't get wifi, I'm not sure if I can get all the files I need to do this upgrade. I'm hoping this upgrade will reconnect me to wifi.
Reading through the Wiki for rooting (http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959), it says I am to use Superuser AND binary, is this correct?
I've found a boatload of Superuser files one the ClockworkMod ROM Manager website, ... which one do I use, there's no explanation?
And I understand I need to install SuperSU AFTER I have it rooted.?.
Regarding an updated OS, from the questions and remarks on this post (http://forum.xda-developers.com/showthread.php?t=1900763), I need both a kernel AND a rom? But other threads I've read say the kernel is in the ROM. Does this mean that CyanogenMod's CM7.2.0 is kernel only and doesn't get you anywhere?
Also from this thread, suggestions were made to upgrade to one kernel, then a rom, then to another kernel and rom, and finally to the kernel and rom the user wants. Why is this necessary?
I have many more questions but they branch off depending on answers to these fundamental questions here.
So, if there's anyone with enough patience and willing to hold my hand through this process, I would greatly appreciate it.
And I need to go cancel my monthly paid warranty fee on this old phone too.
ROMs typically include a kernel in their update zip. CyanogenMod is a ROM and as such includes our own kernel when you install it. Be aware of the 911 issues before upgrading your os to a custom rom.
Sent from my Galaxy Nexus using xda premium
To install Clockworkmod, if you are using Android 2.2 Froyo, go here: http://forum.xda-developers.com/showthread.php?t=833423
Run the "3e_recovery_installer" from your computer with the phone connected and USB debugging mode enabled. Then boot into stock recovery (Hold VOL+ and VOL- and POWER with the phone off, release when you see the logo) and flash the "update.zip" twice. It will boot into a green CWM that temporarily exist until you turn off the phone, beware that this temp CWM only let you flash zips from your Vibrant internal storage, it will not recognize your microSD.
Note: If you are using Eclair 2.1, you should be able flash the update.zip directly without the "3e recovery installer".
You can either flash root from CWM, or download a rom like SlimBean and flash it directly. When you flash a custom rom, it will install a newer version of CWM first (because the older version of CWM will not be able to flash the rom) and the phone will reboot. Take off the battery and put it back, boot into recovery again to see the new version of CWM, then you can install the custom rom again fully this time. Generally you should do a "wipe data and cache" before installing a rom, but sometimes, you might also need to go to "mount and storage" and format the /system folder before you can flash a new rom successfully. This can help avoid system files from your old Android installation to exist and merge with the new rom installation. However, the /system folder is where most of the OS important files are locate so without it the phone won't boot, so you need to have a custom rom in the phone (or microSD) to flash after you format it.
That should pretty much cover most of it. If you ever run into problems you can always use ODIN to recover the phone to factory stock. In fact, if you want to stay with stock and just want your WiFi to get fixed, its probably better to simply do an ODIN recovery (or a factory reset) first, before looking at custom roms.
Most of what I just said is covered in this sticky: http://forum.xda-developers.com/showthread.php?t=849028
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
dar101978 said:
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
Click to expand...
Click to collapse
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
CalcProgrammer1 said:
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
Click to expand...
Click to collapse
Thanks thats what i did, I just basically had to use KIES to use the emergency recovery, then root my phone again. My question is what version of TWRP causes this? cause i used the newest version i could find off GOO. My other concerne is, will it accept or be safe to use a custom ROM? Well i gues ill find out :laugh: THANKS AGAIN!
Everyone with the sgh-i717 is having problems with the latest TWRP and the most stable version is 2.5.0.0. Go with that one or you'll be starting all over again I imagine. And don't just stop at the download link in the OP's, read the thread and find out what's going on. The problems with TWRP have been going on for a while and the development threads have a lot of comments about the latest build causing problems. Good luck! :good:
I've had my brand new SCH-I545 since thanks giving now. I've been trying to root and get a custom ROM on the phone ever since then and have gotten closer and closer but haven't been able to quite get everything to co-operate.
I may catch scorn for posting such a generic question on a flagship phone but I've been up all night for 2 weeks now trying to get this to work following numerous tutorials but with android everything seems to get outdated when there are so many software variables at hand that are constantly changing like firmwares and build numbers. I've included all the info since it all seems to be vital and have tried to seperate tasks by paragraph so you can skip over what you feel may be arbritrary. So if I could get an up to date breakdown on how I could succeed in my endevour I'd appreciate it greatly.
Out the box I have a 4.4.2 and NK1 build number. I was finally able to get root access through towel root after flashing back to NC5. However even after flashing NC5 through odin, about phone still says my baseband and build number end I545VRUFNK1 but towelroot no longer gives me the "phone not supported" message and I'm able to succesfully atain root access, confirmed by root checker. Is that normal?
So I have root now but want a custom ROM. VZW locks the bootloaders on new phones so I believe that means I can't use a custom recovery like CWM. I've tried and tried but it doesn't work, neither does the CWM Rom manager app. I've managed to get a custom recovery through installing BusyBox and Safestrap. (I had to go through several apk's to get Safestrap to work. Usually I would be able to enter TWRP recovery through it but the recovery won't respond to any of my touches. The power button still works to turn the screen on and off so it is not frozen but it won't respond when I swipe to unlock it. Even now that I have it working, if the screen locks I'm unable to unlock it even if TWRP is performing a task in the backround and clearly not frozen.
One time I was able to more or less successfully flash LiquidSmooth (LS-KK-v3.2-2014-10-04-jflte.zip). This was the closest I ever got to my goal as the ROM succesfully booted up and I was able to browse the home screen and change all the settings and it was a moment of joy until I went to settings and switched wifi on it just wouldn't. It either just wouldn't switch or would switch right back and grey itself out I don't remember exactly. My phone had no service either for calls, text or 4G. So everything worked internally it just couldnt comunicate with any signals coming from outside the phone. Why would this be? If I manage to boot LiquidSmooth again is there something I could download to make the wifi/service work? (I could download through USB or Odin.)
After this I tried to flash CM but the phone wouldnt even start after installation and would just bootloop so I had to flash back to stock to make it work again. Then I tried LiquidSmooth several more times but now I get stuck at the bootscreen for LiquidSmooth where it has the logo and the backround flashing. I've let the animation loop for several minutes multiple times before doing a battery pull.
Basically for 2 weeks I've been flashing NC5->rooting->flashing NK1 back->installing safestrap->installing a rom->soft bricking->flashing back to stock ROM and starting again
Is it possible if I keep doing this proccess that it will just work one time? It may sound silly but I kind of believe just because I've had varrying degrees of success following the exact same procedure.
And when I install a ROM in TWRP I go Wipe->(swipe factory reset)->Install->(select LS.zip and wait for it to say its succesfully installed)->Swipe one more time to wipe cache->Reboot after this the phone either fails to start up or loops the LiquidSmooth animation. As I said, one time it started succesfully.
Let me know what any of this information leads you to believe and if you may have a sollution in mind. Huge thanks to anyone that read this and will try to help me. I've had this phone 2 weeks now and would like to start actually using it.
unorthodocks said:
I've had my brand new SCH-I545 since thanks giving now. I've been trying to root and get a custom ROM on the phone ever since then and have gotten closer and closer but haven't been able to quite get everything to co-operate.
I may catch scorn for posting such a generic question on a flagship phone but I've been up all night for 2 weeks now trying to get this to work following numerous tutorials but with android everything seems to get outdated when there are so many software variables at hand that are constantly changing like firmwares and build numbers. I've included all the info since it all seems to be vital and have tried to seperate tasks by paragraph so you can skip over what you feel may be arbritrary. So if I could get an up to date breakdown on how I could succeed in my endevour I'd appreciate it greatly.
Out the box I have a 4.4.2 and NK1 build number. I was finally able to get root access through towel root after flashing back to NC5. However even after flashing NC5 through odin, about phone still says my baseband and build number end I545VRUFNK1 but towelroot no longer gives me the "phone not supported" message and I'm able to succesfully atain root access, confirmed by root checker. Is that normal?
So I have root now but want a custom ROM. VZW locks the bootloaders on new phones so I believe that means I can't use a custom recovery like CWM. I've tried and tried but it doesn't work, neither does the CWM Rom manager app. I've managed to get a custom recovery through installing BusyBox and Safestrap. (I had to go through several apk's to get Safestrap to work. Usually I would be able to enter TWRP recovery through it but the recovery won't respond to any of my touches. The power button still works to turn the screen on and off so it is not frozen but it won't respond when I swipe to unlock it. Even now that I have it working, if the screen locks I'm unable to unlock it even if TWRP is performing a task in the backround and clearly not frozen.
One time I was able to more or less successfully flash LiquidSmooth (LS-KK-v3.2-2014-10-04-jflte.zip). This was the closest I ever got to my goal as the ROM succesfully booted up and I was able to browse the home screen and change all the settings and it was a moment of joy until I went to settings and switched wifi on it just wouldn't. It either just wouldn't switch or would switch right back and grey itself out I don't remember exactly. My phone had no service either for calls, text or 4G. So everything worked internally it just couldnt comunicate with any signals coming from outside the phone. Why would this be? If I manage to boot LiquidSmooth again is there something I could download to make the wifi/service work? (I could download through USB or Odin.)
After this I tried to flash CM but the phone wouldnt even start after installation and would just bootloop so I had to flash back to stock to make it work again. Then I tried LiquidSmooth several more times but now I get stuck at the bootscreen for LiquidSmooth where it has the logo and the backround flashing. I've let the animation loop for several minutes multiple times before doing a battery pull.
Basically for 2 weeks I've been flashing NC5->rooting->flashing NK1 back->installing safestrap->installing a rom->soft bricking->flashing back to stock ROM and starting again
Is it possible if I keep doing this proccess that it will just work one time? It may sound silly but I kind of believe just because I've had varrying degrees of success following the exact same procedure.
And when I install a ROM in TWRP I go Wipe->(swipe factory reset)->Install->(select LS.zip and wait for it to say its succesfully installed)->Swipe one more time to wipe cache->Reboot after this the phone either fails to start up or loops the LiquidSmooth animation. As I said, one time it started succesfully.
Let me know what any of this information leads you to believe and if you may have a sollution in mind. Huge thanks to anyone that read this and will try to help me. I've had this phone 2 weeks now and would like to start actually using it.
Click to expand...
Click to collapse
The issue is that safestrap is incompatible with the roms you are trying to use. It can be only used with Touchwiz based roms(i.e. using the stock kernel). Try flashing hyperdrive rom. Also, Im not familiar if NK1 can use towelroot and safestrap well. My recommendation would be to
1. clean wipe to nc5
2. towel root
3. install safestrap
4. flash ONLY roms that say they were safestrap compatible.
5. Flash any patches, modems, etc.
Weeks? How about spending a few hours reading up on what you can and can't do with your phone.
Raymondlikesroot said:
The issue is that safestrap is incompatible with the roms you are trying to use. It can be only used with Touchwiz based roms(i.e. using the stock kernel). Try flashing hyperdrive rom.
Click to expand...
Click to collapse
Ok, thanks, I was going to try to flash hyperdrive but the ROM I found was 1.2GB and I didn't have that much space on my SD. I'll borrow an empty one and try it again. Is it not odd that LS did a full boot if it's not compatible with safestrap? And are there any other Touchwiz roms? I don't like Touchwiz and am trying to get as far from it as I can but if I could just delete the bloatware (which I can still only disable after towel root), get SD access and get rid of the battery restrictions.
unorthodocks said:
Ok, thanks, I was going to try to flash hyperdrive but the ROM I found was 1.2GB and I didn't have that much space on my SD. I'll borrow an empty one and try it again. Is it not odd that LS did a full boot if it's not compatible with safestrap? And are there any other Touchwiz roms? I don't like Touchwiz and am trying to get as far from it as I can but if I could just delete the bloatware (which I can still only disable after towel root), get SD access and get rid of the battery restrictions.
Click to expand...
Click to collapse
The reason that LS did a full boot is because certain aosp roms can function with a touchwiz kernel. However, the result is always buggy. There is s4 verizon general thread talking about this.
There are many other tw roms. Just go to andriod devlopment! On the top of my head, I can think of eclipse, hyperdrive, echoe, and empty galaxy.
Here's what I did with a new T-Mobile Samsung Galaxy S5:
- Started phone in download mode (started it with Volume Down, Home, and Power buttons) and connected it to computer.
- Started Odin3v185, saw yellow COM box.
- Clicked PDA button and selected philz_touch_6.26.2-klte.tar.md5 file.
- Clicked Start button, flashing went fine, phone reset and everything was cool, still with stock ROM. I was able to boot into Philz recovery to verify that flashing worked.
- As part of my goal of installing XtreStoLite ROM 2.2 (Lollipop), the following steps were to install the modem and bootloader for that ROM.
- Started phone in download mode and connected it to computer.
- Started Odin3.09, saw blue COM box.
- Clicked BL button, and selected G900T-LP-UVU1DOB1-BOOTLOADER.tar.md5.
- Clicked CP button, and selected G900T-LP-UVU1DOB1-MODEM.tar.md5.
- Clicked Start to flash. Phone reset, but it froze at the Samsung logo.
I gave it about a half hour just to make sure it wasn't just taking it's time with this first boot after the update, but it stayed at the Samsung logo. Only way to turn it off was to remove the battery. I'm still able to boot into Philz, so I figured a way to fix it might be to just go ahead and install the ROM. So I selected the "install from zip" option and installed XtreStoLite_ROM_v2.2_LP_XXU1BOD3.zip. Now the startup logo is a bit different, but it still stays frozen at the logo. I know from previous times installing this ROM that it does usually take awhile (maybe 5 minutes) on the first boot after installing, but I let it sit again for about 30 minutes with no luck.
The only thing I can see that I did differently this time, which I know realize was dumb, was skipping the step after flashing Philz where I boot into it and install UPDATE-SuperSU-v2.37.zip to root the device. I thought that I'd be able to install the bootloader, modem, and ROM and end up with a rooted OS, but I'm guessing that rooting is separate from those things, and they can't succeed until the phone has been rooted.
So... what can I do now? I'm trying to install the stock ROM (G900T_TMB_G900TUVU1CNK2_G900TTMB1CNK2_original.zip), but Philz gives me a "installation aborted" error before it even starts, with no other error messages. I also suspect I should install the original kitkat bootloader+modem, but I'm not sure where to find those (searching yields a lot of different results).
Any help would be greatly appreciated. Thanks!
The bootloop must be related to the bootloader/modem you've flashed. SU will allow root access once booted, but it won't prevent the system from booting if you skip it. Are you simply trying to root? FWIW, I'd recommend skipping Lollipop altogether, Marshmallow is night and day better than Lollipop. Flash the complete factory image of one of the Marshmallow releases, then flash your recovery and install SU. There are a couple of good, debloated Marshmallow roms available.
I was able to get out of the situation by flashing a stock ROM from here:
http://forum.xda-developers.com/tmo.../compilation-s5-g900t-stock-firmware-t3042400
I first flashed the stock modem and bootloader, though I'm not sure that was required because I think they're included in the ROM itself.
Used the latest 4.4.2 ROM and NK2 bootloader+modem, just because I'm pretty sure it was 4.4.2 that was on the phone when I got it.
Retried my procedure, this time rooting + disabling KNOX before flashing the Lollipop bootloader+modem from the ROM's install instructions, but I still ran into the same "freeze at boot" problem. I don't know what could be the issue, as I've done this exact procedure with two previous S5s. Not really looking to check out Marshmallow ROMs, just because I'm short on time these days, and after trying out a handful over the years, the XtreStoLite is by far the best for me.... really the perfect combo of stock Android with some of the improvements offered by TouchWiz, with all the tweaks to fix annoying "features" that I want fixed (for example, the removal of that damn "are you sure you want to increase the volume? It could damage your hearing" warning when you connect headphones and try to turn up the volume). Also, just stable and fast, compared to most/all the others I've tried.
Sounds to me as if you need stock Marshmallow with a custom recovery and Exposed. Mine is fast as hell, extremely frugal on battery, and Exposed has got rid of all the annoying TW "features", like the volume warning you mention (also, expanded notifications on lockscreen, battery full notification gone, circle battery, etc, etc). There are also alternatives to stock that are good, I tried one a couple of weeks ago that I think I'm probably going to go back to. Lollipop is horrible after using KitKat, Marshmallow brings back the KitKat experience but with dramatically improved battery life. You'll also get some Stagefright improvements.
Sorry for the delayed response, been too busy to deal with this for a couple weeks. How exactly do I get a stock Marshmallow with custom recovery and Exposed? Don't I already have the custom recovery covered with Philz? What Marshmallow ROM would you recommend? Thanks for the feedback!
Just download & Odin the latest complete image, GPI1, then Odin recovery (since Philz doesn't work, try TWRP, it works for me), then flash SU & Exposed. Takes about 15 minutes, although the download may take longer. Not sure if anyone has posted the link, but you can get it from sammobile, albeit slowly.
invisiblewave said:
Just download & Odin the latest complete image, GPI1, then Odin recovery (since Philz doesn't work, try TWRP, it works for me), then flash SU & Exposed. Takes about 15 minutes, although the download may take longer. Not sure if anyone has posted the link, but you can get it from sammobile, albeit slowly.
Click to expand...
Click to collapse
Did you deodex GPI1 before exposed?
invisiblewave said:
Just download & Odin the latest complete image, GPI1, then Odin recovery (since Philz doesn't work, try TWRP, it works for me), then flash SU & Exposed. Takes about 15 minutes, although the download may take longer. Not sure if anyone has posted the link, but you can get it from sammobile, albeit slowly.
Click to expand...
Click to collapse
Does this thread have the info I need for installing Xposed (I'm assuming "Exposed" and "Xposed" are the same thing)?
http://forum.xda-developers.com/showthread.php?t=3034811
Just install a .zip from TWRP, then install the .apk to manage installed modules?
I have "UPDATE-SuperSU-v2.37.zip". Is that sufficient for SU?
Well dammit, I've now spent multiple hours I didn't have trying to get *ANY* ROM other than the stock KitKat one to work. Was just about to give up after trying one last time with XtreStoLite, this time using KToonsez kernel instead of stock. Restarted and it was taking forever to boot, so I assumed it was frozen and was about to pull the battery and call it a night, when it actually made it into the OS! So perhaps there's something going on with the phone that won't let it boot with any stock kernel, other than 4.4.2. Bummer, because I was starting to get excited about trying Marshmallow.
It's because you have KitKat firmware. You just need to flash the entire MM package first.
What is the MM package, if it's not
G900T-(GPI1)-Bootloader.tar
G900T-(GPI1)-Modem-NonHLOS.tar
G900TUVS1GPI1_G900TTMB1GPI1_G900TUVS1GPI1_HOME.tar.md5
?
You don't need to flash the bootloader & modem separately. If you download the complete firmware, that's all you need to flash, it has all the necessary partitions in it. Just flash that, see if it works, then flash the recovery, etc.
I already tried G900TUVS1GPI1_G900TTMB1GPI1_G900TUVS1GPI1_HOME.tar.md5, both with and without the bootloader+modem packages.
I didn't see any mention of you having tried it in your earlier post. You should be able to flash just that package under AP (All Partitions, I assume), and it should install all the partitions it finds inside the tar. My guess is that Odin isn't completing correctly. What does it say in the log on the left? I had to use Odin 9, 10 wouldn't work on my setup for some reason, nor could I get it to work on XP, only on Windoze 8.