yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 General] djdurban:
I think the real problem with the S5 and to some extent the HTC M8 is not the phones themselves, its the messaging/marketing around them.

Think about when Apple comes up with something new in the display, or the camera, or anything else. It may be incremental but they make it seem like its the greatest thing that has ever occurred on the planet ever. I mean how much time did they spend in the 5S release just talking about the improvements to the camera. Nobody really thought the 5S was a huge disapointment, i mean i aside from the obvious (small screen, etc).

The Asian phone companies have simply terrible product release keynotes, i mean just awful. Samsung's was bad, but HTC's was the most boring release i have ever seen. Why wouldnt Samsung talk up the things they really improved? If for no other reason, at least the echo chamber reviews will mention the differences. I mean, i am a phone junky and have been for the better part of a decade, and i had no idea the display was improved so dramatically. In fact, one of the primary reasons i skipped the S4 was due to the AMOLED that was completely invisible outdoors on the S3.

If i were one of the CEOs of HTC, Samsung, etc, id swallow my pride and change the format of the releases. I might come out introduce the phone, then get of the way and hire a professional presenter to come out and present all the features in a more compelling and detailed manner.
[Galaxy S 5 General] SolarTrans:
Steve Jobs had more stage appeal than all the other tech CEOs combined XD
[Galaxy S 5 General] djdurban:
Indeed, but Tim Cook isnt that great. However, they manage to sell the device better by picking the right things to talk about and by, at least, making it more appealing to watch than say, grass growing ;)
[Galaxy S 5 General] NoteboyTech:
I think it is time i go to a samsung store in India.. and probably try this.. with all of your reviews i am feeling like there is a lot on this phone.. i wanted to buy Note 3.. but I think I will skip it and go for s5.. wish it had 3gb of ram.. just that
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] rpnunez:
I have searched everywhere - Google, XDA, AndroidCentral, everything.

I am very savvy with computers and phones - I'm a programmer myself.

I had CM11 nightly installed for weeks. All of a sudden, my phone restarts itself into an infinite boot loop (doesn't go past the SAMSUNG Galaxy S 4 screen).

I have tried EVERYTHING. Restoring an old nandroid backup, reflashing CM11 and Gapps - nothing.

Every time I try to install the stock firmware - both L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 (acquired directly from Samsung) and L720VPUEMK2_L720SPTEMK2_L720VPUEMK2_HOME.tar.md5 (again, direct download) it always fails at the same spot:

I flashed the MK2 modem when flashing the MK2 stock ROM... no dice. Same thing for the NAE modem + ROM.

Please, help me. I have no clue what to do at this point. The only backup I have, which is of Android 4.2.2, also doesn't work. Same bootloop.

I have tried all of the above things with three different version of Odin: 1.805, 3.04 and 3.07.

I re-installed the Samsung USB drivers, in case that was the issue.

I am completely clueless.

The main problem (I believe) is this:

aboot.mbn

Please and thank you.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] leaderbuilder:
I know this sounds redundant or maybe you've done this too.

Charge the phone fully - while powered off. Take the battery out for

15 earth minutes

. Then run Odin as administrator on your PC 1st (use the full NAE tar put in the PDA slot (in the dev section read the thread for some other tips too)) Then put phone into download mode and then plug into computer

ALSO I know this too sounds silly, but try a brand new USB cable. Can't tell you how many times that has caused problems for me.

Good luck
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] rpnunez:
Thank you for such a quick response!

The phone won't go into the "charging mode" which I know is what you're talking about :(

The USB cable is fine, every time I flash one of the stock ROMs on the phone I have to re-flash the recovery, so we can cross that one off the list.

Am I not using the correct tar file? The file was zipped in a file entitled "Samsung-Updates.com-SPH-L720-SPR-L720VPUAMDC-1365579188.zip" which I downloaded yesterday.

It's charging now in Philz Recovery. Once it's at 100%, I will take out the battery for 15 minutes (hell, probably even 30! lol) and see what happens.

Any other suggestions my friend? Once again, thank you!
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] leaderbuilder:
If your phone had an MJA or later - MK2 or NAE bootloader you CANNOT flash any Odin ROM previous because of the Knox bootloader.

You're trying the MDC - that won't work.

Keep the phone charging and try the NAE

Here is a similar post and similar problem with my response (includes the link to the NAE .tar)
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] rpnunez:
Ahhh... that makes sense.

I just tried flashing the MDC modem, because I believe my 4.2.2 backup is on MDC...but now I have the weirdest message saying "System software not authorized by Samsung has been found on your phone".

Now I think I messed things up...

I'm downloading the NAE file. Hopefully flashing that will fix everything.

Why can't I just delete *everything*? Like a reformat on a Windows PC? Literally, destroy everything - and just flash the stock NAE firmware?

I appreciate your help now so much my friend. Thank you.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] leaderbuilder:
Because of the Knox bootloader you can't wipe everything. Read my other thread as to why. Knox bootloader is in the chips security container and once tripped is not, as of now removable.

Flashing the tar should get you all good to go.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] rpnunez:
I was able to successfully flash to the TAR you linked me to!

However, I am still stuck in a bootloop...

It won't even let me boot into recovery.

You've been such a help buddy. Any other ideas? :(
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] leaderbuilder:
If the tar flashed successfully try power off completely.

Then boot to stock recovery - Power on + Volume up (

kind of tricky on the S4, I

often

miss the right length of time to hold both

kind of freaks me out/pissed me off, but eventually after many battery pulls I'll get it on boot. :P )

Then try a factory reset.

Edit if that fails then try this also:

You can also try to Odin a custom recovery - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltespr/philz_touch_6.08.9-jfltespr.tar.md5 [download mode, odin in PDA slot - do NO check f-reset or autoreboot - once odin is finished do a battery pull]

Then try to get to custom recovery and flash the stock NAE kernel if it doesn't boot

Here's Philz http://xdaforums.com/showpost.php?p=51411121&postcount=1955
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] rpnunez:
Can't get to stock recovery - it just says "RECOVERY BOOTING..." then reboots.

Installed Philz Recovery, installed CF-Auto-Root since Philz complained that I wasn't rooted, when I tried to flash the NAE kernel, it says:

Why me :( :( :(
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] leaderbuilder:
That's okay. Status 7 is an updater script error. There are a few things.

Let's try another kernel.

OR another recovery (I keep multiple recoveries on my externaSD for this reason.

Here is Reverepats TWRP You can flash the recovery from recovery and reboot recovery. Say that five times..

Since you did get to custom recovery you're heading the right way.

Try flashing the stock kernel from the TWRP recovery and

You can try another kernel too.

Ktoonsez' latest kernel is here You can grab the 4.4 TW one (take note of the build prop edit you may have to do to get wifi working - that'll require rooting (cf-autoroo) and a root explorer to get to it)

All seems kernel related to me.

Here is a vid on disabling script checking tha may work too. I relize that it's for full ROMs but it may help.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] rpnunez:
I tried flashing Recerepats TWRP via Philz... no dice. I guess it's just not my day lol. I tried Odin'ing openrecovery (2 versions) and noooo dice.

So I went back to the Philz 6 (I tried flashing Philz 5 and.. no luck), flashed the kernel you linked to, it flashed fine.

....still in a boot loop. I'm so sorry for taking up your time buddy, you've been such a great help.

I'm guessing I should re-odin the NAE tar now, since the kernel has been modified?

I feel like a mechanic who can't change his own car oil lol. I'm a programmer and write PHP/JavaScript daily, none of these things scare me - but nothing is working!
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] leaderbuilder:
Ya,

I'd try re-odining the tar again.

Just put in the pda slot as usual, but this time try unchecking the Auto Reboot and F. reset time. and when done just battery pull and restart.

Edit/Add:

Oh and you might still have to 'factory reset' from stock recovery' if it gets stuck on bootloop.

BUT remember the first boot takes a freaking long time - 5-10 earth minutes for first boot! wait and then try the reset if it doesn't get past it
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] rpnunez:
Just finished re-odinining the tar file. Nothing. Still in a bootloop.

How can my device be so ruined? All I would do is install new CM nightlies - the right way, too. I remember I was in a shopping market yesterday, everything was nice and dandy, and when I get in my car, this bootloop thing started happening,

I'm baffled by this... I really, really am. With your help, along with other things I've tried, I've tried everything under the sun.

The only thing I haven't thought of is using ADB/working on the phone via command line.

What do you think?
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] leaderbuilder:
Worth a shot.

One thing though.

Before you give up pull the battery again for about 15+ minutes. then put it back in and then try to Odin. I had to do that on my old Epic a few times.

Couldn't hurt to try adb.

One last thing - in custom recovery (philz say) wipe the cache and then wipe the Dalvik cache (in advanced I think) then try booting again. Sometimes that helps bootloops.

But for sh*ts and giggles how about trying to install a custom ROM? Maybe Negalites's Here's his release version

To install boot to Philz recovery; wipe cache, wipe dalvik and the wipe to install new ROM/Factory reset then select the negalite.zip and run throught the install.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] leaderbuilder:
[MENTION=2333802]rpnunez[/MENTION] haven't seen a post back. Hope you got it going.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] rpnunez:
Leaderbuilder, thank you so much for following up like that - it really means alot! :cowboy:

Unfortunately, I tried your latest suggestions, and still nothing - both unchecking Auto Reboot and F. Reset Time + battery pull for 15 mins, and the wiping of the cache and dalvik cache.

I should try flashing a custom ROM, but may I ask why flashing CM + Gapps would be different? I've tried flashing CM countless times :/

Also, could any of this be happening because of Knox? I've read about Knox, but I don't really know much about it. Before I posted this thread, I downloaded a multi-tool kit (Dr. Ketan's Multitool v6 - I followed this guide: http://techbeasts.com/2014/01/17/how-to-deknox-samsung-galaxy-s3-s4-note-2-note-3/) and it was to "reset" the Knox counter, but it didn't get me out of the boot loop.

I just wish there was a "Format" function for my phone lol. Is there anything else you can think of? I really don't understand how a phone can get so... destroyed. No water damage, no fall, nothing - from one moment to the next, boot loop.

Would the stock recovery help? When I flash the NAE tar, I hold Volume Up + Power, I see "RECOVERY BOOTING..." and then... boot loop! Can that give any clues?

What's odd is that it won't go past the Samsung Galaxy S4 screen - it's like a computer not being able to go past the BIOS screen.

Once again, I greatly appreciate your time and effort.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] leaderbuilder:
Well you can Odin a custom recovery again. And wipe the crap out of everything - caches, system, DATA for sure do that, wipe to install new ROM. (if you use TWRP - there is an option to use rm vs format which may help in advanced I think.)

Then flash Philz maybe and again try another ROM like Negalite

I'm pretty stumped but that's what I'd do - wipe the sh*t out of it, reboot recovery wipe again then try installing ROM.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] rpnunez:
It's really odd that I can't flash any recovery other than PhilZ "philz_touch_6.25.0-jflte.tar.md5". I can't even flash a slightly older version, "philz_touch_5.18.2-jfltespr.tar.md5". Hell, I've tried all of these:

OUDHS-Recovery-jfltespr-1.0.3.3.tar

openrecovery-twrp-2.7.0.1-jfltespr.tar

openrecovery-twrp-2.6.3.0-jfltespr.tar

clockworkmod_6.0.3.2_jfltespr.img

GalaxyS4-CWM-6.0.4.4-Sprint.tar

openrecovery-twrp-2.6.0.0-jfltespr.tar

And NONE of them work.

In PhilZ, I formatted everything (wipedata, wipe to install new rom, formatted /boot, /preload/ cache, /system, everything that can be formatted - flashed NAE tar again and nothing.

I'm going to go ahead and try to flash Negalite's ROM. I'm about to just take the damn phone to Best Buy because luckily have I have insurance on it... but geez, I really cannot fathom what is going on with this device. But I still want to try a few more things.

Do you know of any ADB commands/guides or something that can perhaps generate a "log file" as to what's going on during the boot process? Or something to that effect?

Thank you for your time my friend. :angel:

Edit/Update:

Flashed Negalite's ROM... nothing. I'm getting tired of looking at the Samsung Galaxy S4 boot screen lol.

Would using "Re-partition" help? Maybe something got partitioned? I'm really running out of ideas..
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] leaderbuilder:
Okay, by chance is your device the T model? - the Triband one?

Because I can see and think of no reason why all this wouldn't work unless it was not the Sprint SPH-L720.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] rpnunez:
I do believe it is the Triband one... it has a SIM card, and I remember seeing options like "GSM, GSM/CDMA, GSM/CDMA/LTE" when selecting network mode or w/e it's called. Is there a way to determine if it is Triband?
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] leaderbuilder:
AAAHHH. SH&T.

Well, then that changes everything! [for the worse actually]. I was under the impression that you had the regular L720

You can check by removing the batter and looking at the Model #. It will have the T right after the L720.

You cannot flash items made for the SPH-L720 to the SPH-L720

T

. Dang it. Here is the thread for that phone.

If that is the case your best be might be having a Sprint service tech use their flashing tool to get it back to zero - reload the right stock ROM with their tool. You can still root with the latest CF-Autoroot and there are some recoveries that work too.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] rpnunez:
Actually, I just removed the battery, and effectively, it is SPH-L720 (no "T").

:/

I just re-flashed Negalite's ROM, with the Negalite Kernel, (earlier it was with the Stock NAE Kernel), and still nothing.

I think it's time to just give up, eh? I really don't think there is anything I can do. You've been so helpful, I don't think anyone else would have an idea either - you've had the best ideas.

Edit:

My "KNOX WAARANTY VOID" is set to "0x1"

I've tried using the Deknoxer, but it always thinks my device is the Galaxy Note 2.

Does that give you any insight?
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] leaderbuilder:
phew! Glad to here we havent been fighting a non starter

The 'de-knoxer' only removes the 'software' knox stuff. NOT the actual bootloader.

You knox flag is 0x1 becuase when you installed the recovery for CM it tripped it. Rooting by itself dosen't trip the counter, but flashing a custom recovery (anyone) does.

I'm flippin stumped. You've done everything I'd do save throw it at a wall. :P

I'd take to sprint and say, hey there was some update thingy and my phone is dead, can you help.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] rpnunez:
Ah well. I was about to just smash the screen lol I'm so frustrated at this phone.

It's worth a shot taking it to Sprint I suppose, but my plan is with Best Buy, I have insurance on it and they fix the phone for free, but it takes 3 days and I have to put a $50 deposit for a crappy flip-phone, and when the phone is fixed they return the $50.

*Long, exhausting sigh* I guess that's what I'll do.

It has been a pleasure going through this process with you buddy. I hope you don't mind me befriending you here on XDA, you truly are a very nice and special person.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] leaderbuilder:
Well if you got it at BestBuy, they usually have the ability to just flash the lates Sammy/Sprint firmware. You may be in luck.

I just wish I knew what the delio is, you've done everything I'd do.

They are (if you find the right guy/gal) usually very cool about doing this in the store for you without charge in about 15mins.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] KingBrandon:
Similar Problem on my SPH-L720

I just started rooting and adding custom ROMs. I downloaded 5 different ones this week. I tried to get the Pacman Rom Black Power Edition and it has an installer. Halfway through the process, my screen froze and then turned black. Now I cannot boot my phone up or into philz cwm recovery. Now I am trying to flash a stock recovery using Odin, but it only fails. My message is the same (I think).

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> aboot.mbn

<ID:0/003> NAND Write Start!!

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

On my phone:

Odin Mode

Product Name: SPH-L720

Current Binary: Custom

System Status: Custom

Knox Kernel Lock: 0x0

Knox Warranty Void: 0x1

CSB-Config-LSB: 0x30

White Protection: Enable (in grey text)

eMMc Burst Mode enabled (in grey text)

Start [224, 1440] (in red text)

SV Rev. Check Fail: fused: 5, Binary:1
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] cruise350:
MDC is the oldest firmware for our phone and you can not install it because you have the knox enabled bootloader which means that your phone has at least the MJA or newer firmware. You will need to install either the MJA, MK2 or NAE software to fix your phone. The problem is, you need to know what firmware you were on. If you were on 4.4.2 before the problem, flash the NAE stock tar. If you were on 4.3, then flash the MK2 stock tar file. Anything older will fail.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] chefbaker11:
Might be a silly question but have you tried flashing a recovery tar via Odin? I.e....stock/philz/TWRP/CWM? Find the newest baseband version In a custom ROM, like nae or mk2. So try flashing the recovery file via odin then either allow auto reboot (mine went straight in to new recovery) or reboot manually into NEW recovery and do a FULL WIPE OF EVERYTHING. Then try flashing via the new recovery, the new ROM. This worked for me when nothing els would. I hope it helps. Just remember, no downgrading stock Roms when coming from 4.4.2. because of knox and the new file structure put in place by kitkat. They are no longer compatible, for a lack of a better word. Good luck!
[One (M8) General] Mr Hofs:
​

Conversion guides

My GSM Conversion Guide (Convert to any GSM Variant of m8)

Convert from most GSM varants to lollipop sense

thanks to [MENTION=4348417]fma965[/MENTION]

MID conversion guide thanks [MENTION=3437245]scotty1223[/MENTION]

GPE to Sense conversion guide thanks to [MENTION=3468692]grentuu[/MENTION]

Another GPE to Sense conversion guide (with RUU) thanks to [MENTION=2588346]djluisbento[/MENTION]

Convert fully back to stock guide thanks [MENTION=2258271]EddyOS[/MENTION]

​

Q : How do i find the correct info on which stock nandroid i need for my device

A : You perform these fastboot commands to get the needed info

- fastboot getvar all (gives the whole devices info list)

- fastboot getvar version-main (gives only the main version number as output)

- fastboot oem readcid (gives only the CID as output)

Match the main version number and the cid with the nandroid backups and you will have the correct one !

Q : How do i restore the stock nandroid backup

A : In general :

- Place the nandroid backup unpacked on the sdcard of the phone in the right backup folder

* Philz touch uses - Clockworkmod\Backups\

* TWRP uses - TWRP\Backups\ or TWRP/Backups/serialnum/ (replace serialnum with your device's serial number. To have TWRP create the proper directory structure for you, just do a simple backup of just the boot partition and put the backup files in there) thanks to garyd9 for the additional info :)

- Flash the boot.img or boot.emmc.win file from the nandroid backup

- Make a full wipe in the recovery

- Restore the nandroid backup and reboot

Q : The restored nandroid backup is still rooted but i want to unroot it

A : Download this unsuperuser file and flash it via the custom recovery Thanks to jbeez & SaHiLzZ

Q : Can i apply an official HTC OTA on my stock rooted rom

A : Yes but the system apps (carrier branded apps included) has to be 100% intact

Q : Can i apply an official HTC OTA with a custom recovery

A : No you need your stock recovery (at least one that starts with the same base number)

Q : Are stock recoveries compatible to nandroid backups with other main and cid numbers to install official OTA's

A : At this point i believe so (it was on the hox) but they have to start with the same base (IMPORTANT!!!!!! THIS WON'T WORK WITH LOLLIPOP BASE RECOVERIES SEE HERE thanks [MENTION=830797]ckpv5[/MENTION]

- Example :

stock recovery 1.12.771 is the same as 1.12.401

stock recovery 1.54.401 is the same as 1.54.206

Q : How do i flash a recovery.emmc.win file made by the TWRP recovery

A : you flash it with the following command :

- fastboot flash recovery recovery.emmc.win