Hello folks,
I'm a developer who is writing system-near software for rooted Android-devices.
My program works on nearly every device, but the AT&T SGH-I377 S4 is different from all other devices and there my software is not working.
I've got a european S4 I9505 and just tried to flash the whole "I337UCUAMDB_I337ATTAMDB_ATT.zip" via Odin on my device (after nandroid & full wipe).
But sadly Odin told me "FAIL (auth)" and nothing more happened, so it seems I can not "just flash" the I337-rom on my I9505.
Has anyone any tip how I can do this? I don't need the phone for talking and so on - WIFI & ROOT is fully enough to debug my application.
After I got my application then working, I would just reflash my old ROM.
Glad for any advices & with kind regards,
Martin
Related
Sup guys. I have a problem with my S4. I doubt anyone will be able to help me find a fix but its worth a try. I hope someone will help.
Anyway, I flashed my GT-i9500 (Galaxy S4) from 4.2.2 to 4.3. Now it doesnt boot, It just gets stuck at the 2nd boot screen. Its not even a bootloop. It just hangs there. The S4 sound that plays gets cut like halfway.
I tried flashing a lot of different ROMS, and it still does the same thing. When I rooted it, I noticed the boot welcome sound plays full, but it still hangs after that.
I used Philz Recovery and mounted all the folders etc, but efs says invalid. So that means the EFS folder is messed. I get that, but I cannot repair the EFS if I cant boot the phone, I need the Samsung MTP **** for Samsung Tool to work. I have an N7100 (Note 2) Where I repaired the EFS with Samsung Tool, I was able to boot the phone.
I looked ALL over the net including this forum and found nothing. Right now the phone is just worth nothing. This is my last option, to ask here myself. If it cant be fixed I just cut my losses and get another phone.
I also flashed a PIT file, CSC file, Modem file during the period I was trying to get this fixed. If anybody knows this problem, It'll be very helpful.
Thanks.
you could try upgrading to 4.4, i have all the files for omega v21
heres the link for all the stuff from my google drive.
https://drive.google.com/folderview?id=0B_trhAurRvdmb0RkNGpoTkVNU0k&usp=sharing
instal the bootloader and phone file via odin, bl = bootloader cp = goes into the phone part of odin
then fash the rom via philz recovery, worth a try !!
good luck
That wouldn't work, thats for the Snapdragon variant I think. The i9505. I have the i9500. I'll download the Omega ROM for i9500 and try it anyway.
Thanks.
Still doesnt work.
StickyBomb said:
Still doesnt work.
Click to expand...
Click to collapse
Did you tried complete of phone, than power and vol up, at the buzz lose vol up and at loge lose power button.
and then flash with odin bl. and modem
etc.
I've flashed with Odin & Recovery.
I flashed another bootloader, XXUEMK8 & Odexed Knox Free Stock ROM XXEUMK8 & it still does the same. I dont know whats wrong with it.
Another thing I forgot to mention is if I root it using Odin, the welcome sound plays full and it hangs, and if I reboot it, the welcome sound goes back to cutting off again.
This phone probably cant be fixed. I dont know wtf's wrong with this phone. This is WORSE than hard bricked.
oh & as I mentioned before, I have a Galaxy Note 2 & had an EFS problem with it. I fixed it, the difference was this Note 2 actually booted properly with any ROM installed. I used a Z3X Box & Samsung Tool to fix up the EFS. Maybe this problem is only with i9500 or with i9500 & newer models.
Eeeer don't mean to point out the obvious here but you did do a factory reset in stock recovery after flashing stock 4.3 in Odin? That's all you needed to do at the start.
When I went from 4.2 to 4.3 I couldn't get it to boot at all unless I performed factory reset after flash.
Sent from my GT-I9505 using XDA Premium HD app
I came from a rooted Samsung org. rom 4.3 to omega v21.1 Android 4.4.2
After this i tried slimkat, and had from first start the same issue, no booting.
Nothing works
only starting with power and vol. up as descried above, I could flash XXUFNA5 bootloader & modems.
After this twrp.
And at last I flashed S4 Google Edition - 4.4.2, a ROM for the Samsung Galaxy S 4
Thanks for the help people.
I gave up on trying. I tried everything even factory reset after flashing, different ROMS, different Android versions. 4.1.2, 4.2.2 & 4.3. Today I ended up selling the phone's LCD. Atleast I didnt everything. lol. Wouldn't be buying another Samsung EVER. I was thinking I need another box and stuff, like NSPRO but I dont have that.
Hi, thanks for reading this.
I recently tried to flash the Hyperdrive rom RL15 on my Galaxy s4 i337m. I had a stock 4.3 mk6 firmaware and since its a m model the bootloader is unlocked. I rooted the phone, installed TWRP 2.7, Factory wiped and flashed the rom itself with the ATT compatibility pack. Unfortunately after starting the phone, it went into downloading mode, with a message on the left side saying that couldn't do normal boot. I'm trying to understand where the problem is, and any input would be appreciated.
FIXED IT : Installing the T-Mobile compatibility pack instead of ATT comp. pack fixed the problem and let my phone boot with no problem.
Cant find it
zontiq said:
Hi, thanks for reading this.
I recently tried to flash the Hyperdrive rom RL15 on my Galaxy s4 i337m. I had a stock 4.3 mk6 firmaware and since its a m model the bootloader is unlocked. I rooted the phone, installed TWRP 2.7, Factory wiped and flashed the rom itself with the ATT compatibility pack. Unfortunately after starting the phone, it went into downloading mode, with a message on the left side saying that couldn't do normal boot. I'm trying to understand where the problem is, and any input would be appreciated.
FIXED IT : Installing the T-Mobile compatibility pack instead of ATT comp. pack fixed the problem and let my phone boot with no problem.
Click to expand...
Click to collapse
Could you please tell me where you found the Compatibility pack for T-mo? i cant find it anywhere. :/
Hello everyone, i'm a new member. I apologize if my english is not good enough.
After been driven insane by one pre-installed app from my Operator (Claro Peru) i decided that it was time to root my device to get rid from that pest. I'm a noob, so i started to investigate about the safest methods to not damage my phone. My Device's model is SGH I337m.
The plan was to update the FW from JB 4.3 that came with my phone to 4.4.2 and then proceed to root. I downloaded the Canadian 4.4.2 FW with build version I337MVLUFNC1 and installed manually with Odin. After the phone rebooted, my S4 was upgraded with 4.4.2 but Samsumg keyboard was going insane, so i went to the apps and solved that cleaning the cache/data. Then i noticed that the Wifi wasn't connected, i tried to turn it on, but then a message with a shield appeared saying that my device security stopped the operation. Beliving it was only a problem with KNOX, i installed autoroot (CF-Auto-Root-jfltecan-jfltevl-sghi337m) with Odin, open SuperSU and stopped it from working, but the Wifi still wouldn't connect.
So the first thing that crossed my mind was to unroot and do a factory reset, didn't work. The FW still was 4.4.2, so i´ve been searching solutions with this FW because i've read some cases of devices that stopped working completely after trying to do a downgrade. so i don't want to go to that route for now.
After a couple hours of search, some solutions i found on the forum were:
- Install Faux123 Kernel (Found on Youtube, this would be the thread i think http://forum.xda-developers.com/showthread.php?t=2273437http://forum.xda-developers.com/showthread.php?t=2273437
- Flash a modem for i337m
- Safestrap recovery and bypasslkm.zip
- Downgrade
I haven't tried any of this methods because i dont want to get into a deeper trouble. In the first solution i'm not sure what to do because this is the files the author recommends for canadian models (i337m), but when i enter here http://faux.romhost.me/jflteatt/jb42/http://faux.romhost.me/jflteatt/jb42/ only jflteatt appears, and that would be i337 model, isn't it? I thought that installing it may cause more troubles, so i didn't do it.
For the flashing modem method, i'm not really sure if installing a modem from another country would get me in trouble, so again i didn't proceed.
I found the Safestrap and recovery method on a downgrade thread for the i337, so again, didn't do it.
So, is there a way to get one of this methods working on i337m to get wifi working again, or is there any other better method to get back wifi.
I would really appreciate any help you can give me guys.
Copellius said:
... My Device's model is SGH I337m.
The plan was to update the FW from JB 4.3 that came with my phone to 4.4.2 and then proceed to root. I downloaded the Canadian 4.4.2 FW with build version I337MVLUFNC1 and installed manually with Odin. After the phone rebooted, my S4 was upgraded with 4.4.2 but Samsumg keyboard was going insane, so i went to the apps and solved that cleaning the cache/data. Then i noticed that the Wifi wasn't connected, i tried to turn it on, but then a message with a shield appeared saying that my device security stopped the operation. Beliving it was only a problem with KNOX, i installed autoroot (CF-Auto-Root-jfltecan-jfltevl-sghi337m) with Odin, open SuperSU and stopped it from working, but the Wifi still wouldn't connect.
So the first thing that crossed my mind was to unroot and do a factory reset, didn't work. The FW still was 4.4.2, so i´ve been searching solutions with this FW because i've read some cases of devices that stopped working completely after trying to do a downgrade. so i don't want to go to that route for now.
After a couple hours of search, some solutions i found on the forum were:
- Install Faux123 Kernel (Found on Youtube, this would be the thread i think http://forum.xda-developers.com/showthread.php?t=2273437http://forum.xda-developers.com/showthread.php?t=2273437
- Flash a modem for i337m
- Safestrap recovery and bypasslkm.zip
- Downgrade
I haven't tried any of this methods because i dont want to get into a deeper trouble. In the first solution i'm not sure what to do because this is the files the author recommends for canadian models (i337m), but when i enter here http://faux.romhost.me/jflteatt/jb42/http://faux.romhost.me/jflteatt/jb42/ only jflteatt appears, and that would be i337 model, isn't it? I thought that installing it may cause more troubles, so i didn't do it.
For the flashing modem method, i'm not really sure if installing a modem from another country would get me in trouble, so again i didn't proceed.
I found the Safestrap and recovery method on a downgrade thread for the i337, so again, didn't do it.
So, is there a way to get one of this methods working on i337m to get wifi working again, or is there any other better method to get back wifi.
I would really appreciate any help you can give me guys.
Click to expand...
Click to collapse
ok so you have the i337m canadian version... making anything related to safestrap and the att i337 irrelevant, completely different methods so don't get them confused lol
you were updating from stock 4.3 right? your best bet is to factiry reset and reflash stock fw for 4.4.2 before you brick your device... kitkat is very different from 4.3, maybe read up on it a bit too...
for ex, the "message with a shield appeared saying that my device security stopped the operation" isn't related to needing to root, it's an option under security settings.
to enable superuser on kitkat you need to enable developer options, then enable superuser. I prefer supersu so manually install that from play store afterwards. I recommend checking and/or enabling this as soon as the phone completes booting up after flashing.
also I think there's a known issue w/ 4.4.2 and wifi not turning on until after 2nd boot completed if I rememebr correctly, been using 4.4.4 for awhile now though so could be wrong...
good luck and check out the help section :angel:
Hi all,
This is probably the #4829 post with identical topic, a very common issue, but unfurtunately this time i wasn't able to solve it alone so any help will be appreciated.
I own a i9506 (LTE-A edition) S4. until now with a 4.3 ROM.
I was forced to encrypt the device by Microsoft Exchange services and lock it with a code, after a while i decided it's time to upgrade to a new firmware and downloaded a brand new ROM which i found in xda.
I flashed twrp and the new rom, rebooted the device and viola, it freezed on the i9506 logo screen. i tried a different kernel which led me to the code locking screen, every time i tried to type something, it gave me "keyboard stopped" error.
So i decided it's good time to do a full format, so i downloaded an original stock rom for i9506 4.4.2 I9506XXUCNJ1_I9506NEECNJ1_I9506XXUCNF3_HOME.tar.md5 flashed it with Odin (using AP) still, the same issue. tried to do full wipe through original recovery instead of twrp, every time i flash original recovery i'm not able to login to it.
i'm pretty much stuck with flashing and wiping, any idea where to go from here?
Thanks!
Is it carrier locked, and what carrier if it is?
Hello all,
I recently discovered that my S5 was only running KitKat despite Marshmallow having been released for it. I checked for OTA updates and it found nothing, so I decided to flash a custom 6.0 ROM onto it (and for some reason I ended up deciding not to make a backup of the phone beforehand, the ultimate mistake).
The problem became that it didn't recognize Tracfone for my service provider and wouldn't connect to the mobile network. I then downgraded it to a 5.0 ROM, and it no longer even recognized the SIM card, saying there was none.
So I tried to flash the original stock ROM a few times, but every time either got errors from ODIN, the phone itself, or the TWRP bootloader.
Long story short, I seem to have screwed up multiple times trying to install a ROM to get around KitKat and now my phone appears to be softbricked. I can get into the TWRP menu and the "download" mode, but when trying to start the phone, it sits on the "Samsung Galaxy S5" screen with the "Set Warrenty Bit : kernel" text at the top left.
I'm just wondering if there's a way to fix it at this point, or if I've completely trashed the phone.
If anybody has suggestions or experience with this, all help is welcome!
Thanks!
MevNav said:
Hello all,
I recently discovered that my S5 was only running KitKat despite Marshmallow having been released for it. I checked for OTA updates and it found nothing, so I decided to flash a custom 6.0 ROM onto it (and for some reason I ended up deciding not to make a backup of the phone beforehand, the ultimate mistake).
The problem became that it didn't recognize Tracfone for my service provider and wouldn't connect to the mobile network. I then downgraded it to a 5.0 ROM, and it no longer even recognized the SIM card, saying there was none.
So I tried to flash the original stock ROM a few times, but every time either got errors from ODIN, the phone itself, or the TWRP bootloader.
Long story short, I seem to have screwed up multiple times trying to install a ROM to get around KitKat and now my phone appears to be softbricked. I can get into the TWRP menu and the "download" mode, but when trying to start the phone, it sits on the "Samsung Galaxy S5" screen with the "Set Warrenty Bit : kernel" text at the top left.
I'm just wondering if there's a way to fix it at this point, or if I've completely trashed the phone.
If anybody has suggestions or experience with this, all help is welcome!
Thanks!
Click to expand...
Click to collapse
Are you sure you have the stock firmware for the 902l and not the 903vl? The reason you didn't get the update for 6.0 is you have the 902l model. If you had the 903vl model you'd have 6.0. Straight talk never released it for the 902l model. No idea why being both models are very similar. Im not sure but if you make it back to stock on kitkat. I think you can use safestrap from the Verizon s5 to use some custom roms that run kitkat. If your bootloader is in fact unlocked and you can install a custom recovery other then safestrap. I believe you can install pretty much anything but I'm pretty sure straight talk ships the phones with the Toshiba chip so the bootloader isn't unlockable