Database Users

HELP!!

So I recently rooted my LTE Tab 10.1 after some errors on my part. I finally got root, and the bootloader unlocked (thanks to six5alive's post here) Here's what I have:
CWM recovery
unlocked bootloader
Rom Manager installed
SU permissions
I've tried flashing two different ROMs, and both flash without a problem. But when I attempt to reboot, I get the Samsung logo and a yellow triangle below it, and then the tablet shuts down. At first I thought it was just the ROM, but after flashing two, I'm getting suspicious. I have a Nandroid backup of the stock rooted ROM, and that restores & boots properly every time.
What am I doing wrong?

You might have root but from the sounds of it the tab does not like the insecure kernel hence the yellow triangle on the logo screen. On a tab, I am not sure how to get around this.
Why not run stock and use TiBu to get rid of the bloatware until you can find a solution? Keep a Nandroid of bone stock then another for your custom settings...

Mardenator said:
So I recently rooted my LTE Tab 10.1 after some errors on my part. I finally got root, and the bootloader unlocked (thanks to six5alive's post here) Here's what I have:
CWM recovery
unlocked bootloader
Rom Manager installed
SU permissions
I've tried flashing two different ROMs, and both flash without a problem. But when I attempt to reboot, I get the Samsung logo and a yellow triangle below it, and then the tablet shuts down. At first I thought it was just the ROM, but after flashing two, I'm getting suspicious. I have a Nandroid backup of the stock rooted ROM, and that restores & boots properly every time.
What am I doing wrong?
Click to expand...
Click to collapse
What roms did u flash...?
Sent from my GT-P7500 using XDA App

Strange, when I flashed the ISI-Galaxy rom on my P7100 i got then same thing as you, when i turned the device off it automatically went back on with the same result. I had the idea that i was going to have to bring it back to the shop for repairs but... This happened while i was at work. So i placed the Tab in my backpack but when i got home a half an hour later the device was functioning again. So maybe yours needs some time to get over this 'boot up'.

ZangetsuNX-01 said:
Strange, when I flashed the ISI-Galaxy rom on my P7100 i got then same thing as you, when i turned the device off it automatically went back on with the same result. I had the idea that i was going to have to bring it back to the shop for repairs but... This happened while i was at work. So i placed the Tab in my backpack but when i got home a half an hour later the device was functioning again. So maybe yours needs some time to get over this 'boot up'.
Click to expand...
Click to collapse
Tried this, got the same result I've been getting..

I flashed these, wiped after flashing each one obviously.
http://forum.xda-developers.com/showthread.php?t=1372432
and
http://forum.xda-developers.com/showthread.php?t=1155023
Both caused the triangle issue, so I just restored the rooted stock ROM I'm running.

Mardenator said:
I flashed these, wiped after flashing each one obviously.
http://forum.xda-developers.com/showthread.php?t=1372432
and
http://forum.xda-developers.com/showthread.php?t=1155023
Both caused the triangle issue, so I just restored the rooted stock ROM I'm running.
Click to expand...
Click to collapse
Next time please use the edit button.
I think I have an explanation as to why its crashing. The ISI-Galaxy Rom and P7500XWKK4 Galaxy Tab 10.1 / HC 3.2 ROM are for the P7100 model. Yours is the SCH-I905 model so the roms you tried to flash are incompatible.

Just realized that ZangetsuNX-01 is right, I've been flashing WiFi-only ROMs, not ROMs for the Tab 10.1 LTE. Downloading http://forum.xda-developers.com/showthread.php?p=17858660#post17858660 now, will flash and post results here asap.

UPDATE: got a leaked TW ROM to install via Odin and boot, posting this from the tablet. Added a screenshot for kicks.

BTW, for anyone with an LTE Tab, flash this via ODIN NAO!!!!
http://rootzwiki.com/topic/10463-ro...x-leak-build-for-vzw-galaxy-tab-101-lte-only/
It's unrooted, with stock recovery, but you can follow the directions on the page to get root, it's simple. Just Odin a recovery .tar file, go to recovery, flash SU zip, and voila. Running it at 1.4GHz max, 1GHz min, and it's awesome. TouchWiz is also a nice step up from stock HC.

@Mardenator
your screenshot a looke liek from my adwluncher from my tab...

Lol I'm using ADW Ex.

ok i dont untersant waht you with them post, sorry.

Conan179 said:
ok i dont untersant waht you with them post, sorry.
Click to expand...
Click to collapse
I'm not sure what the question here is, but I was suggesting that if you have an LTE Galaxy Tab 10.1, you should flash the ROM that I provided a link to. It's a good ROM, and I've been running it for 2 days now.

Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General

Every custom ROM restart issues, eventually bootloops

over the last few days I've flashed a number of ROMs, mostly the Google Edition 4.2.2 and 4.3 ones and every single one of them eventually fails to boot hanging on the Samsung bootloader screen. and i say eventually because the first boot is almost always flawless, but then each time i reboot or power down, its almost guaranteed to loop.
I've tried so many different combinations that there's really not a single path I've taken every time, but the general steps are:
-root original firmware using motochopper
-install TWRP via GooManager
-reboot recovery and wipe everything, typically I do Advanced and select everything, then format Data
-then flash through ADB sideload, I do this since I wipe everything before flashing and I don't have an external SD card
-immediately after flashing ROM, I flash loki-doki also through ADB sideload. some of the ROMs I tried said they were lokied, but I still got the ATT invalid ROM message, so I reflashed with loki and it worked.
-then reboot system and the first time it comes up and works fine on every ROM I've tried
But if I power down or restart, on a very rare occasion it'll come up, but almost every time it hangs on bootloader screen. I also noticed once it's stuck on bootloader, power button becomes unresponsive, sometimes holding it powers down device, sometimes does nothing (have to press and hold twice)
If I flash back to stock using Odin, it works, boots, reboots, powers down just fine.
I've also tried flashing with a ROM and then immediately after with the stock ATT kernel, also booted up fine, but looped on restart.
Could this be hardware issue?
I'm about to give up on this and go back to stock for good, which would be really disappointing, can anyone help?

Flash a KT kernel and see what happens, I suppose you know which one correct?

TheAxman said:
Flash a KT kernel and see what happens, I suppose you know which one correct?
Click to expand...
Click to collapse
I assume KT means http://forum.xda-developers.com/showthread.php?t=2292341 ?
I've tried that too with jamal2367's 4.2.2 GE ROM (http://forum.xda-developers.com/showthread.php?t=2341794). It refused to boot all together.
First time I flashed with AOSP version since I thought that was an AOSP ROM, then reading more comments in the other thread it said I needed the TW version for GE ROMs, so I tried that too. Either way, neither of them booted at all, even the first time, so I gave up on KT and only used either ROMs' included kernels or ATT stock.

It is not a hardware issue, I am guessing that you have a US ATT G4 correct? I would odin back to stock, and restart the process again, this is assuming you tried the correct TW kernels. Because I know this error and all it requires is a simple flash of the correct kernel.

TheAxman said:
It is not a hardware issue, I am guessing that you have a US ATT G4 correct? I would odin back to stock, and restart the process again, this is assuming you tried the correct TW kernels. Because I know this error and all it requires is a simple flash of the correct kernel.
Click to expand...
Click to collapse
OK I'll try one more time from scratch, can you verify I'm using the right stuff though for US ATT Galaxy S4:
ROM: http://forum.xda-developers.com/showthread.php?t=2341794
Kernel: http://forum.xda-developers.com/showthread.php?t=2292341 (TW one, specifically http://goo.gl/SiDjB)
And any idea why the ROM's kernel wouldnt work after being lokied?

collegebored said:
OK I'll try one more time from scratch, can you verify I'm using the right stuff though for US ATT Galaxy S4:
ROM: http://forum.xda-developers.com/showthread.php?t=2341794
Kernel: http://forum.xda-developers.com/showthread.php?t=2292341 (TW one, specifically http://goo.gl/SiDjB)
And any idea why the ROM's kernel wouldnt work after being lokied?
Click to expand...
Click to collapse
You know, I don't even look at anything that says loki anymore, I flash the rom I want and use MY carriers kernel, bootloops and hangs are just not there, I do not see these issues everyone has, because, I have this procedure everytime. So...
Btw, your good on your files you want to flash, but, if this does not work ie, GE and that kernel, try a TW rom with the kernel, bet it boots properly. I do not give a rats
a$$ about goole roms. They are not worth it. Btw, I use this procedure on TW and aosp roms, no issues. Just because it says it loki'ed, flash the kernel you know works, loki just confuses people.
The Ax says again an again..My opinion only!
Good luck sir.
BTW, I ran that rom with the kernel you chose, it should work just fine. Remember, flash the TW version.
Thanks Ax for your help here, your welcome.

Phone stuck on "Samsung - Custom" screen after creating TWRP backup. Help please?

Phone stuck on "Samsung - Custom" screen after creating TWRP backup. Help please?
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks

Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.

Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

Tylorw1 said:
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
I don't see how that could be the case. I didn't flash anything. I just loaded TWRP, created a backup, and rebooted my phone. No ROM\kernel change. Nothing more than creating a backup in TWRP.
scott14719 said:
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Click to expand...
Click to collapse
I tried searching, the closest one I could find on the first few pages was this one. I just didn't see any specific to my situation because nothing was flashed. Like my response to Tylorw1, all I did was boot into recovery, create a backup, and reboot my phone. Didn't flash a ROM, change a kernel, format anything, etc...

I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app

Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...

STVERDI said:
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
TheAxman said:
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
Click to expand...
Click to collapse
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.

a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.

Simonzi said:
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
Click to expand...
Click to collapse
And you have to be ****ing kidding me. I rebooted into recovery while typing my initial response, just to verify I was still on the 2.5.x.x TWRP. Booted up TWRP, verified that, choose "Reboot System", and same thing. Back to sitting at the Samsung screen. Nandroid backups or not, ditching TWRP as soon as I get it able to boot back up.

Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download

somebody had mentioned this...
http://forum.xda-developers.com/showpost.php?p=44629460&postcount=8
make sure you have the correct firmware and proceed as you are. likely your best bet.

Simonzi said:
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
Click to expand...
Click to collapse
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).

scott14719 said:
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
Click to expand...
Click to collapse
Yeah, I meant 1.6gb firmware package. Just forgot the "gb". That's what I'm currently downloading, but trying to recover it with Kies while waiting.

I would like to report I had the same problem.
After changing roms and making a nandroid, and then deciding to switch roms again, I ran into the stuck at Samsung Custom with a lock boot screen. Most roms would boot up once, but a restart or power down would lead to being stuck. I was flashing through TWRP.
I went into TWRP and flashed OUDHS recovery which overrode TWRP and wiped/flashed through OUDHS a new rom.
Problem solved.

S3 at&t stuck in TWRP booting screen.
xBeerdroiDx said:
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Click to expand...
Click to collapse
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t

Lnjames said:
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Click to expand...
Click to collapse
Wrong forum. Please go to the s3 section with your question.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Had this problem just now, solved it by fixing permissions.

I am running an MDL based S4, and screwed the pooch. I was going to wipe the internal storage and made the mistake of doing it through TWRP 2.5. Now, I have the same problem of being stuck on the custom boot screen. I have tried to change from TWRP to OUDHS Recovery, but still boot loops to Custom screen. I have tried fresh installs of 4.2 ROMs and 4.4.2 Google Editions. Do I need to flash via ODIN?
Flame away....I know better than this!!!!
Help would be greatly appreciated.
Sent from my GT-N8013 using Tapatalk 4

[Q] Help a noob, cannot boot after trying to flash stock rom

So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.

rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.

rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware): https://mega.co.nz/#F!0JdRkIZR!AqqKdbvba_Hpg5VrCmrbPw

i7vSa7vi7y said:
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.
Click to expand...
Click to collapse
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.

silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Does it matter that I can't get into recovery to clear the cache first before trying new roms?

silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Maybe I'm doing something foolish but every time I try to download files from the link you gave I get a decryption error so I can't download them zip or original.

rmngorelov said:
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.
Click to expand...
Click to collapse
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing

i7vSa7vi7y said:
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing
Click to expand...
Click to collapse
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.

rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
Depends what recovery you had and what version. I personally like Philz touch recovery but TWRP is good. Now wipe and flash a ROM my friend or restore a backup

rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
im having similar issues. which version of TWRP worked for you?
thank you

fearthemarchx said:
im having similar issues. which version of TWRP worked for you?
thank you
Click to expand...
Click to collapse
I recommend flashing the newest one here using odin
http://teamw.in/project/twrp2
Then once you are able to boot into recovery go to wipe and perform both factory reset and format data. Then install whatever rom you like, I used Sprint Galaxy S4 SPH-L720 VPUFNAE (Androdi 4.4.2) found here
http://galaxys4root.com/galaxy-s4-stock-firmware/ (or maybe find a newer stock rom if this one gives you errors)
Just copy the zip file to the phone, boot into twrp, do wipe factory reset again, select install then select the zip in whatever directory and you should be good to go. Make sure you do a back up in twrp once you get the phone to boot so you can always revert to stock.
I hope I was thorough enough that some of the information was useful. Let me know if you need any more help.

only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app

fearthemarchx said:
only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
Format with philztouch that works then try flashing a new stock rom with odin. That should bring everything back to stock including the recovery.

ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app

fearthemarchx said:
ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
You're in download mode when you flash from odin right? If you your getting an error flashing, try a different stock rom after reformating/resetting to factory (it's crucial to clear the cache before trying a different rom). I had to try a few roms before I found one that worked.

[Q] Galaxy S5 Dev Edition (Verizon) TOTALLY WIPED

im in big trouble on this one, i rarely EVER ASK FOR HELP, but this time im done. i was on fusion 4.4.2 and decided i wanted to try lollipop. so i found the dev edition roms and tried loaading the with philz recovery. got it up and running but only had data NO MOBILE SERVICE. so i started loading different roms with no luck, tried different kernels thinking i mismatched them. still no luck so i tried couple different modems NO LUCK!!!!!!!!!!!!! got totally lost, upset and agarvated. well thats when i made a BIG BIG MISTAKE. i boot in philz touch and went to advanced menu i formatted EVERYTHING data, system, media EVERYTHING. now i load (thru odin) fresh Philz recovery found the ODIN TO STOCK thread have tried loading ALL the dev files complete stock firm, the kernel modems EVERYTHING. it takes on the phone but when it reboots gets stuck on GALAXY S5 sceen. still says custom and has unlock but wont boot up. so i go back into recovery go to load zip menu and alls thats on my phone is /0 folder and /clockmod folder. so the phone is wiped out and wont take anything thru odin. i can still get to philz but no way to get zip into phone to load. PLEASE TELL ME i didnt lock my bootloader????????? i really need some help here been working on this thing for 3days now. thanks in advance

1tonv said:
im in big trouble on this one, i rarely EVER ASK FOR HELP, but this time im done. i was on fusion 4.4.2 and decided i wanted to try lollipop. so i found the dev edition roms and tried loaading the with philz recovery. got it up and running but only had data NO MOBILE SERVICE. so i started loading different roms with no luck, tried different kernels thinking i mismatched them. still no luck so i tried couple different modems NO LUCK!!!!!!!!!!!!! got totally lost, upset and agarvated. well thats when i made a BIG BIG MISTAKE. i boot in philz touch and went to advanced menu i formatted EVERYTHING data, system, media EVERYTHING. now i load (thru odin) fresh Philz recovery found the ODIN TO STOCK thread have tried loading ALL the dev files complete stock firm, the kernel modems EVERYTHING. it takes on the phone but when it reboots gets stuck on GALAXY S5 sceen. still says custom and has unlock but wont boot up. so i go back into recovery go to load zip menu and alls thats on my phone is /0 folder and /clockmod folder. so the phone is wiped out and wont take anything thru odin. i can still get to philz but no way to get zip into phone to load. PLEASE TELL ME i didnt lock my bootloader????????? i really need some help here been working on this thing for 3days now. thanks in advance
Click to expand...
Click to collapse
Factory reset after flashing back to stock?

*Detection* said:
Factory reset after flashing back to stock?
Click to expand...
Click to collapse
tried that AT LEAST three times no luck

You should be able to recover from any problem scenario you cause in recovery, using ODIN
Stock ROM from sammobile, maybe you'll need a PIT file to re-partition the phone, there is a thread on XDA in these S5 forums with PIT files
EDIT - 2nd post
http://forum.xda-developers.com/showthread.php?t=2737448

After wiping everything AGAIN and letting it sit on galaxy screen it finally booted up. 1st thing I did was made a backup now I guess I'm gonna do A BUNCH MORE READING them I'll get this thing rooted and try some other rooms. Seems there's the A08 I'm on then NK2, N12 and other versions and seems only certain roms use certain kernels and firmware. So I need to get the right configuration for each b4 even trying to install them or they don't boot up.

A lot more to this galaxy s5 unlike my Nexus in the past. B4 just load the rom and go. With this s5 a lot more things to do and know about. All part of the game I guess