Database Users

[Q] S4 stuck on boot Splash Screen. Odin keeps failing. pls help!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have a Sprint Galaxy S4, i received the OTA update to 4.3 and when my phone began to restart it crashed. I tried to ODIN back to stock but I keep getting the error shown below. I even tried using Samsung Kies, but when it asks for the S/N number, It keeps saying its invalid
Does anyone know how to fix this problem!?!?!?
Pls help..ive already been without a phone for 2 days, and I dont have the time or resources to take it to the sprint store.

x_maniic said:
I have a Sprint Galaxy S4, i received the OTA update to 4.3 and when my phone began to restart it crashed. I tried to ODIN back to stock but I keep getting the error shown below. I even tried using Samsung Kies, but when it asks for the S/N number, It keeps saying its invalid
Does anyone know how to fix this problem!?!?!?
Pls help..ive already been without a phone for 2 days, and I dont have the time or resources to take it to the sprint store.
Click to expand...
Click to collapse
I'm in the same boat! I've tried everything ADB to stock, using update.zip in recovery everything and I keep getting e:signature failed someone please help us pretty please

x_maniic said:
I have a Sprint Galaxy S4, i received the OTA update to 4.3 and when my phone began to restart it crashed. I tried to ODIN back to stock but I keep getting the error shown below. I even tried using Samsung Kies, but when it asks for the S/N number, It keeps saying its invalid
Does anyone know how to fix this problem!?!?!?
Pls help..ive already been without a phone for 2 days, and I dont have the time or resources to take it to the sprint store.
Click to expand...
Click to collapse
shanda5303 said:
I'm in the same boat! I've tried everything ADB to stock, using update.zip in recovery everything and I keep getting e:signature failed someone please help us pretty please
Click to expand...
Click to collapse
once on 4.3 you cannot odin back to 4.2.2 because the boot loader will block it.
Go to the general forum and download the 4.3 tar from the op of this thread and you will be good to go
http://forum.xda-developers.com/showthread.php?t=2522810

neudof said:
once on 4.3 you cannot odin back to 4.2.2 because the boot loader will block it.
Go to the general forum and download the 4.3 tar from the op of this thread and you will be good to go
http://forum.xda-developers.com/showthread.php?t=2522810
Click to expand...
Click to collapse
I will Try this right away! Standby for results. And thanks!!!

The MJA update worked for me thanks!!
Sent from my SPH-L720 using xda app-developers app

[Q] about "Recording Failed"

i get the error "Recording Failed" when i pressed the record button.... my sd card and phone memory still have like 10gb empty... and im using Phronesis Rom v3.0. Any solution?

what do logs say

what logs do you mean?

the logs that tell you what the error is

DSA said:
the logs that tell you what the error is
Click to expand...
Click to collapse
im not sure where to find it...i just saw the pop out error when i press the record camera icon..

aronron33 said:
im not sure where to find it...i just saw the pop out error when i press the record camera icon..
Click to expand...
Click to collapse
XDA is a developers forum/site. Not an end-user forum/site.
People are expected to search for the info the need first.
So google your issue, if that not works google howto get the right logs.
If that also doesn't succeed, write down what you have done to avoid the error.
Don't forget to put in all the needed specs, software versions and so on.
And do that in a proper post, preferably with good spelling, grammar and punctuation.
If done all that, help will be more helpful, plentiful and faster.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i cant switch to the video camera mode...

I'm out

@aronron33 Yeah you dug your own grave on this one.
You will get NO HELP, if you dont read others comments and at least try.
So bubye and goodluck finding out the problem yourself!!!

HanZie82 said:
@aronron33 Yeah you dug your own grave on this one.
You will get NO HELP, if you dont read others comments and at least try.
So bubye and goodluck finding out the problem yourself!!!
Click to expand...
Click to collapse
wow you are so helpful........i google -ed and i cant find anything about extract the logs... so i have no idea what the problem is and i cant even switch to the video camera mode so how could i get an error logs?

aronron33 said:
wow you are so helpful........i google -ed and i cant find anything about extract the logs... so i have no idea what the problem is and i cant even switch to the video camera mode so how could i get an error logs?
Click to expand...
Click to collapse
I have the same problem on my N900W8, probably you can fix it installing a 5.0 bootloader.

So I solved it by:
Using Odin 3.11.1
I have already tried Factory reset, wipe cache, wipe dalvik, flashed the latest stock Lolipop or older lollipop with ODin and nothing solved the problem.
So I tried to flash the latest stock lolipop with Odin and marking checked (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update).
I suspect that the Phone EFS clear did the trick. It's function is related to the modem and radio of the phone. And clearly the modem has a problem here.
I hope this will help anybody out there having this issue.
This problem happened after trying to flash lollipop using FlashFire app to reserve the root that I had in my previos Android KK 4.4.2.
Phone: Galaxy Note3 N9005 Malaysian

Why can I add a new APN on Nougat?

Title says it all.
I no longer had the "+" on top in Access Point Names to add a new one?
I have a fresh install of Nougat and a factory reset.
Not rooted and bootloader locked.
Anyone else see this problem?
Steve

I don't have that problem. I'm on NRD90U, everything stock. What's your build number?

Same build number as you.
Are you on Verizon?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I can also add APN fine. Same build, AT&T. Can you edit that one?

1. Unlock your bootloader
2. See #1

dratsablive said:
1. Unlock your bootloader
2. See #1
Click to expand...
Click to collapse
I was able to add a new APN before Nougat without being bootloader unlocked?
What do you mean by "See #1"?

BackInA88 said:
I was able to add a new APN before Nougat without being bootloader unlocked?
What do you mean by "See #1"?
Click to expand...
Click to collapse
What I meant is just Unlock your bootloader and leave it that way. You'll be thankful when you run into trouble flashing updates and or custom roms, etc.

dratsablive said:
What I meant is just Unlock your bootloader and leave it that way. You'll be thankful when you run into trouble flashing updates and or custom roms, etc.
Click to expand...
Click to collapse
I use to flash ROM's all the time.
But I have been happy with stock and use Android Pay all the time and would rather not have to deal with the problems that goes with getting it to work with root.
I may unlock and flash the new Nougat factory imgs as I ADB'd the OTA.
Maybe that has something to do with my problem?
I also installed the Pixel Launcher but I don't see how that come have effected my problem?

You can be on stock without root and still keep an unlocked bootloader.

Unlocked the bootloader and fastboot flashed everything, no joy!

Thinking about giving this a try?
*2767*3855# - Think before you give this code. This code is used for factory format. It'll remove all files and settings including the internal memory storage. It'll also reinstall the phone firmware.

I just looked at my wife's 5X with Nougat is it doesn't have the "+" either on the APN?
Maybe it has something to do with Verizon?

So iirc google now downloads the apns for your carrier on first boot, and I know some carriers lock out apn editing. Not sure if that happens with this device though.

S7 Edge (Sprint) stuck in boot loop after attempting to root using Odin

Welp, I'm pretty sure I messed this up. Found a YouTube video (not even sure which one at this point, sorry) that was recently uploaded detailing how to root a Galaxy S7 Edge. Downloaded the firmware, opened up Odin, put it into Download mode, selected the Qualcomm firmware version for the AP field, and click start. It flashed correctly (according to Odin) and the phone began restarting and didn't stop. Just show's the "Galaxy S7 Edge" screen, goes black, and starts over.
I tried downloading the stock firmware for Sprint, load the appropriate files into Odin, and click start, I then get this output:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And on the phone, I see:
My build number is NRD90M.G935PVPS5BRA1, kernel version 3.18.31-12623509
I'm fairly certain this is entirely something that could have been avoided had I read more guides or instructions. Unfortunately, here I am! I really appreciate any help anyone can give me. I've been Googling and reading all morning, and I'm sure the answer is there, but I'll be damned if I can see it.

While I don't think there's much important info here, I figure it's at least showing some more in terms of version and name:

Your binary boot is v5. It won't work and you can't downgrade at the moment. What are you trying to do with root? There are many non root alternatives. To fix your bootloops, odin the stock firmware again.
Make sure you have the special version of odin too.
Also, download the stock firmware again. Try updato.com or plug the firmware version into android file host

lvpre said:
plug the firmware version into android file host
Click to expand...
Click to collapse
I don't know why I did not put together the relevance of firmware and the build number, but that was the issue all along it seems! After a dozen different cables, ports, and firmware versions I finally realized I needed to plug in the whole build number to find the firmware for that build specifically. Once flashed, the phone rebooted, asked to restore the backup based on the Google account, and it can text and make calls! Thank you so much for the help, I really appreciate it. I'll be sure to read and research a lot more before the next attempt to root a phone.

reddeth said:
I don't know why I did not put together the relevance of firmware and the build number, but that was the issue all along it seems! After a dozen different cables, ports, and firmware versions I finally realized I needed to plug in the whole build number to find the firmware for that build specifically. Once flashed, the phone rebooted, asked to restore the backup based on the Google account, and it can text and make calls! Thank you so much for the help, I really appreciate it. I'll be sure to read and research a lot more before the next attempt to root a phone.
Click to expand...
Click to collapse
Glad it worked out...we all have been there at some point. Any reason you wanted to root? There may be some non-root alternatives available.

lvpre said:
Glad it worked out...we all have been there at some point. Any reason you wanted to root? There may be some non-root alternatives available.
Click to expand...
Click to collapse
Mainly I was just wanting to get rid of the stock Sprint bloatware that you can't uninstall by default. If you've got any other suggestions for it, they're very much appreciated!

I have some t350's with issues recovery/MDM/black screen and bootloops

I recently found at the dumps a box of t350's 6/18 didnt like combination flashing the mdm away/new firmware install. 3 failed the same way while putting on newest firmware with odin now they say mdm mode in odin again and i have no debug access. 1 black screens in bootloader and when booting no debug access mdm mode in odin again. BUT ! I have 1 with debug access and see it in ADB BUT it fails to install due to signature verifcation of the ROM's I've tried. I think the later is savable EZ just need a a little help getting TWRP onto it I guess and I'm good. I'll worry about the others later but any ideas ? my brain hurts from trying cables/roms/adb versions lol

Maybe the rom is incorrect have you checked the region and model number etc?

Kenora_I said:
Maybe the rom is incorrect have you checked the region and model number etc?
Click to expand...
Click to collapse
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time

TDIfrogman said:
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time
Click to expand...
Click to collapse
no matter what i write to it twrp any firmware just fails like it did when it was mdm locked

Could you provide ODIN logs?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

it shows mdm locked and the odin log reflects that BUT they where unlocked at some point im, afraid to try and flash the other and they'll end up like this one

TDIfrogman said:
View attachment 5364601
Click to expand...
Click to collapse
They might have NAND flash erros because they arent able to write to it.

Kenora_I said:
They might have NAND flash erros because they arent able to write to it.
Click to expand...
Click to collapse
hmmmm how can i fix it ?

It could be hardware issue, I'm not sure how to fix hardware issues. Thats probably the reason they were all together in a box.

no they where in a box because they came from a school and they didn't take knox off, there was 1000+ of them I just grabbed a tray full they have these crazy polycarbonate cases on them too with security screws. they all worked until i flashed knox away with varying results 12/18 working fine 18 worked prior but in knox

Oh that info is noted.
May I help you later. Its pretty late and I have to get off.
Ill help in the mornin