Related
RESOLVED
I ran the RUU for my phone, re-ran the update and am stable on 1.08.652.11 710RD
Original post:
I'm getting a consistent kernel crash on all kernels, stock, etc. after the latest HTC update for sprint-vm cdma. Basically, I can get any rom to boot, after about 10-30 seconds, kernel crashes causing the phone to reboot.
I've attached the dmsg log that contains the crash information.
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?
wendall911 said:
I'm getting a consistent kernel crash on all kernels, stock, etc. after the latest HTC update for sprint-vm cdma. Basically, I can get any rom to boot, after about 10-30 seconds, kernel crashes causing the phone to reboot.
I've attached the dmsg log that contains the crash information.
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?
Click to expand...
Click to collapse
Try stock kernel if that crashes then custom rom
Sent from my One V using xda app-developers app
cybervibin said:
Try stock kernel if that crashes then custom rom
Click to expand...
Click to collapse
Stock kernel and all custom roms, ICS and JB have the same exact result. This is why I'm suspicious that this was a bad firmware update. I've read several posts about spontaneous reboots, but most people don't know about dmesg, so I don't have anything to compare to.
wendall911 said:
Stock kernel and all custom roms, ICS and JB have the same exact result. This is why I'm suspicious that this was a bad firmware update. I've read several posts about spontaneous reboots, but most people don't know about dmesg, so I don't have anything to compare to.
Click to expand...
Click to collapse
Does it happen like this?
http://www.youtube.com/watch?v=IIqT-xd0AqU&feature=youtu.be
I have the same issue man. It's bizarre.
patbushnell said:
Does it happen like this?
I have the same issue man. It's bizarre.
Click to expand...
Click to collapse
Yes, this is the same behaviour. I'm not sure if you're able to dump the dmsg stuff from adb, but certainly same crash. Typically the phone network status shows a little x, right before the reboot. But the lagginess starts happening when the 5 second kernel reboot is issued.
I've tried to change to airplane mode, disable sdcard and everything else I can think of, still crashing and I'm not able to make much of the logging info
When you applied the OTA were you completely back to stock. Like locked bootloader and stock recovery?
sentfromybrain
aaronrw said:
When you applied the OTA were you completely back to stock. Like locked bootloader and stock recovery?
sentfromybrain
Click to expand...
Click to collapse
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.
wendall911 said:
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.
Click to expand...
Click to collapse
You will surely get the RUU to make your phone working perfectly. That's what I did.
patbushnell said:
You will surely get the RUU to make your phone working perfectly. That's what I did.
Click to expand...
Click to collapse
Confirmed RUU -> Update worked the second time. This is probably the safest method. This appeared to work initially, but clearly did not. Thanks for all the feedback!
I can't get any non-stock rom to boot after applying the OTA update. Well ok it boots but loops after about 10-15 seconds.
I have to RUU it and not apply the update to get any non-stock rom to work.
CDMA/VMUSA here.
---------- Post added at 09:24 PM ---------- Previous post was at 09:19 PM ----------
wendall911 said:
Confirmed RUU -> Update worked the second time. This is probably the safest method. This appeared to work initially, but clearly did not. Thanks for all the feedback!
Click to expand...
Click to collapse
So are you able to run any other roms without reboots? Or are you only on stock?
MasterTec said:
I can't get any non-stock rom to boot after applying the OTA update. Well ok it boots but loops after about 10-15 seconds.
I have to RUU it and not apply the update to get any non-stock rom to work.
CDMA/VMUSA here.
---------- Post added at 09:24 PM ---------- Previous post was at 09:19 PM ----------
So are you able to run any other roms without reboots? Or are you only on stock?
Click to expand...
Click to collapse
I applied the OTA update. Only the stock kernel (after update) will boot now. Any non-stock kernel crashes - always seems the last line is rmt_storage, which the IPC to shared memory of the boot loader I believe.
Noob question
wendall911 said:
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.
Click to expand...
Click to collapse
Can you link me to a working RUU?
i got my one v primoc back in the beginning of summer, but then something fell on it and cracked the screen super bad but i loved the phone so much that i bought another at the end of october. i unlocked, wiped, and flashed JB roms... which seemed to work fine for a while & then would have issues of staying stuck in roaming. i've tried different roms. i never had this issue with my first one v... could my new one have the update already when i bought it? i ran the RUU football posted and was able to boot the stock rom... but right away it goes into roaming again, with my phone not even recognizing that it's using a VM service.
real confused...
jetfactor said:
i got my one v primoc back in the beginning of summer, but then something fell on it and cracked the screen super bad but i loved the phone so much that i bought another at the end of october. i unlocked, wiped, and flashed JB roms... which seemed to work fine for a while & then would have issues of staying stuck in roaming. i've tried different roms. i never had this issue with my first one v... could my new one have the update already when i bought it? i ran the RUU football posted and was able to boot the stock rom... but right away it goes into roaming again, with my phone not even recognizing that it's using a VM service.
real confused...
Click to expand...
Click to collapse
Yes it's possible that you got one with the update already on it however the problem you are having is completely different than the problem we're describing in this thread and could be caused by many other things - not necessarily the OTA update.
Seems a bit off topic for this thread...
More of the rebooting problem
I have 2 phones one with this problem, the other without it. My friend got one of these phones after i installed jelly bean on mine. He had it long enough to have updated the firmware using the stock image. I made a backup of the stock image, but it seems to have been corrupted (zero byte .zip file). I need to get the phone working (stock or updated, at this point there is no preference so long as it works)
In the bootloader, the radio version of the crashing one is:
1.00.00.0928
The working one is:
1.00.00.0521_2
As far I can tell, this is the only difference. I Used the same SD card and the same procedure for wipe/installing the OS with the same files.
Have you found a solution to this? If so, can you point me to the downloads/instructions for how to fix it?
Looking for help
wendall911 said:
RESOLVED
I ran the RUU for my phone, re-ran the update and am stable on 1.08.652.11 710RD
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?
Click to expand...
Click to collapse
This may be a bit noob-ish, but can you please add instructions with links for any downloads. I am new to android hacking and have not yet picked up all of the short hand.
Thanks!
madhephaestus said:
This may be a bit noob-ish, but can you please add instructions with links for any downloads. I am new to android hacking and have not yet picked up all of the short hand.
Thanks!
Click to expand...
Click to collapse
hey can i please know how to fix the radio on my phone i have the same problem, my phone will boot and turn on but after 10 seconds in turns off again and boots again? can i please get help ?
tl;dr I have a blue LED showing up in the top left of the phone and nothing showing up on the screen after the SAMSUNG logo appears. I do hear the Sprint 4G LTE music, but that's it. The screen is off.
NOTE: I'm running Sprint's stock 4.1.1 ROM rooted.
Other threads I looked at (neither is the same issue):
http://forum.xda-developers.com/showthread.php?t=581929
http://forum.xda-developers.com/showthread.php?t=1792477
I had my first OTA update appear today. When I ran the update, Clockwork showed up and upon hitting "Yes", it failed. I looked around online and found this guide to reverse my rooting: http://www.epiccm.org/2012/06/sprint-sgs3-stock-restore.html
I was able to successfully flash TeamEpic-RemoveRoot-from-Recovery-signed.zip, but I didn't hit the keys right for the next one and ended up booting into the OS.
After restarting the phone, I hit the right keys and started ODIN. I saw COM show up in blue and put the TeamEpic-Sprint-SGS3-stock-boot-and-recovery.tar.md5 file in the PDA area then hit Start. I got a green PASS and then closed Odin and waited.
The phone had a black screen with that blue LED in the top left. I waited a while and then just powered it off. Took out the battery and tried again, same thing; although, the SAMSUNG logo does show up. It turns off when the Sprint part is supposed to show and at that moment I can hear the audio but the screen turns off. In this mode, the phone gets very very hot.
I can still boot into the stock recovery, but I can't do much else.
I just wanted the OTA . Does anyone know what might be happening?
EDIT: I put Clockwork Recovery back on, and then Advanced Recovered the boot part of a backup I did before this mess. Surprisingly, that worked. Problem is, I still haven't gotten the OTA working.
Ideas?
Just odin the stock tar
Sent from my SPH-L710 using xda app-developers app
CrfEpic4g said:
Just odin the stock tar
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
What do you mean by that? Which stock tar?
I think the latest tar we have is still Lj7 but idk. just flash the lj7 tar in odin and update to the latest ill try and find it for you
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 08:50 AM ---------- Previous post was at 08:47 AM ----------
http://www.hotfile.com/dl/161492098/9fa8372/L710VPALEN_L710SPRALEN_SPR.zip.html
Theres a link to lj7 just download that flash it in odin and youll be back to stock. Then all you have to do is update to mb1.
Sent from my SPH-L710 using xda app-developers app
Saturn2888 said:
tl;dr I have a blue LED showing up in the top left of the phone and nothing showing up on the screen after the SAMSUNG logo appears. I do hear the Sprint 4G LTE music, but that's it. The screen is off.
NOTE: I'm running Sprint's stock 4.1.1 ROM rooted.
Other threads I looked at (neither is the same issue):
http://forum.xda-developers.com/showthread.php?t=581929
http://forum.xda-developers.com/showthread.php?t=1792477
I had my first OTA update appear today. When I ran the update, Clockwork showed up and upon hitting "Yes", it failed. I looked around online and found this guide to reverse my rooting: http://www.epiccm.org/2012/06/sprint-sgs3-stock-restore.html
I was able to successfully flash TeamEpic-RemoveRoot-from-Recovery-signed.zip, but I didn't hit the keys right for the next one and ended up booting into the OS.
After restarting the phone, I hit the right keys and started ODIN. I saw COM show up in blue and put the TeamEpic-Sprint-SGS3-stock-boot-and-recovery.tar.md5 file in the PDA area then hit Start. I got a green PASS and then closed Odin and waited.
The phone had a black screen with that blue LED in the top left. I waited a while and then just powered it off. Took out the battery and tried again, same thing; although, the SAMSUNG logo does show up. It turns off when the Sprint part is supposed to show and at that moment I can hear the audio but the screen turns off. In this mode, the phone gets very very hot.
I can still boot into the stock recovery, but I can't do much else.
I just wanted the OTA . Does anyone know what might be happening?
EDIT: I put Clockwork Recovery back on, and then Advanced Recovered the boot part of a backup I did before this mess. Surprisingly, that worked. Problem is, I still haven't gotten the OTA working.
Ideas?
Click to expand...
Click to collapse
Why are you so intent on taking the OTA? Freeza has a stock rooted ROM over in his thread. And if you want just update the baseband, just flash the "MB1 Firmware/modem/baseband update" file in the aforementioned thread.
If you're already rooted with a custom recovery (which you were/are), there's no reason to unroot just to flash the OTA. Freeza typically has his stock rooted ROM updated with the OTA within a week of it being released. In my area OTAs are kind of late, so he typically gets it out before I even see the notification.
So, in summary. OTAs are not required, XDA (and Freeza in particular) has you covered.
topherk said:
Why are you so intent on taking the OTA? Freeza has a stock rooted ROM over in his thread. And if you want just update the baseband, just flash the "MB1 Firmware/modem/baseband update" file in the aforementioned thread.
If you're already rooted with a custom recovery (which you were/are), there's no reason to unroot just to flash the OTA. Freeza typically has his stock rooted ROM updated with the OTA within a week of it being released. In my area OTAs are kind of late, so he typically gets it out before I even see the notification.
So, in summary. OTAs are not required, XDA (and Freeza in particular) has you covered.
Click to expand...
Click to collapse
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Saturn2888 said:
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Click to expand...
Click to collapse
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Saturn2888 said:
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Click to expand...
Click to collapse
Setting >scroll all the way to the bottom >about phone>read what it say there. If it says your on latest then it should be ok you may have to clear some things and if it doesn't say latest just edit the build prop.
Go to this thread by Cnexus and follow all instructions http://forum.xda-developers.com/showthread.php?p=39627397
Transmitted with a portable device using Xparent Blue Tapatalk 2
Saturn2888 said:
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Click to expand...
Click to collapse
Are you on MB1 or MA6?
Just flash an updated rom, or follow the instructions in my OTA thread for how to get rid of it
Saturn2888 said:
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Click to expand...
Click to collapse
If you dirty flash the rom over whatever you had before, it should not affect any settings
CNexus said:
Are you on MB1 or MA6?
Just flash an updated rom, or follow the instructions in my OTA thread for how to get rid of it
If you dirty flash the rom over whatever you had before, it should not affect any settings
Click to expand...
Click to collapse
MB1 as of now. What do you mean by dirty flash the rom?
edfunkycold said:
Setting >scroll all the way to the bottom >about phone>read what it say there. If it says your on latest then it should be ok you may have to clear some things and if it doesn't say latest just edit the build prop.
Go to this thread by Cnexus and follow all instructions http://forum.xda-developers.com/showthread.php?p=39627397
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I think the message isn't showing up anymore bc it hasn't bugged me at all today. Device Status is and has always been "Modified" anyway.
Thanks!
Saturn2888 said:
MB1 as of now. What do you mean by dirty flash the rom?
I think the message isn't showing up anymore bc it hasn't bugged me at all today. Device Status is and has always been "Modified" anyway.
Thanks!
Click to expand...
Click to collapse
A dirty flash is when you flash without clearing anything, and that's why no data is lost when you do one of those. However it can lead to issues, so i would advise against it when possible
CNexus said:
A dirty flash is when you flash without clearing anything, and that's why no data is lost when you do one of those. However it can lead to issues, so i would advise against it when possible
Click to expand...
Click to collapse
Yeah, last time I did that, the system wouldn't boot.
After several hours of trial and error, I found a way that worked for me. It will trip the Knox counter though. Also, what worked for me may not work for everyone else. If you brick your device that's not my fault in any way, so good luck
Using this guide, flash back to the stock TAR (not the UVUAMDL TAR). This restores 4.2.2, which allows access to the menu. However, this alone is not enough, as it won't give you access to the perso functions. Attempting to flash the UVUAMDL TAR will result in an error (at least, it did for me).
Second, extract the modem.bin from the UVUAMDL file, and flashed it to the phone using Odin. It's similar to the guide above, but instead of using PDA, you use phone. This gives you access to the perso functions, as it forces the baseband back to UVUAMDL from UVUEMK2. It may be possible to flash the UVUAMDL.tar modem files found in other threads, I haven't tried this out myself though.
Now, at this point you can follow the instructions in this thread, as every option should now be available. If they're not, make sure your Android version is 4.2.2 and that the baseband is UVUAMDL.
If it works at this point, great, go on to the next step (you may have noticed by now that your sound is not working). If not, use RegionLock Away to fully unlock the phone. At this point, your phone should be fully unlocked and you can see it connected to the network. However, dialing/calling lags significantly, and there is no sound.
The next step is to use Odin to fully restore UVUEMK2, which would restore full functionality. You can download the file from here, and flash using the same steps above. This will restore full sound and phone functionality, while your device remains unlocked. If it gets stuck during the boot animation, you simply need to do a factory wipe from recovery (not sure if this works, haven't tested it myself), or just install your recovery of choice from Odin and install whatever ROM you want to use (what I did, which still required a full factory reset from recovery). Skipping restoring UVUEMK2 and installing your ROM of choice does not work, however. You will still have no sound and the phone function will lag considerably.
If everything goes well, you should have a fully unlocked T-mobile Galaxy S4.
Better guide by kali323:
kali323 said:
1. Download MDB Tar. Extract from 7zip file and then rename the file (remove the .md5) so the filename should be "SGH-M919-UVUAMDB-k0nane.tar"
http://www.hunterspad.com/Domains/S...ir=Xda/Galaxy+S4/T-Mobile+S4/Return+To+stock/
2. Odin the MDB Tar in the PDA slot and once it finish go to recovery and factory reset.
3. It will take forever to reboot and it will be stuck at the boot up screen for awhile with this error "Kernel is not seandroid enforcing set warranty bit: Kernel". In about to 5-10 mins it will boot up.
4. Now youre in MDB 4.2.2 with MK2 modem.
5. Odin the .bin file below. Use the PHONE slot in odin and not PDA. Again it will take 5-10 mins to boot up with the error "Kernel is not seandroid enforcing set warranty bit: Kernel"
https://mega.co.nz/#!S9AjUAYA!GOOIp2B4z5dIZy2RFxwQBsMz_v7nRJiOypoAjkuAwtc
6. Now you have MDB Rom with MDL modem
7.Odin CF AutoRoot with the link below in the PDA Slot. It will take 5-10 mins to boot up with the error "Kernel is not seandroid enforcing set warranty bit: Kernel"
http://download.chainfire.eu/328/CF-Root/CF-Auto-Root/CF-Auto-Root-jfltetmo-jfltetmo-sghm919.zip
8.Download RegionLock Away 1.3 App either in the thread below or buy it at the google play store to support the developer
http://forum.xda-developers.com/showthread.php?t=2470551
9. Run RegionLock Away and click reboot now. It will take another 5-10 mins to boot up and if you dont ask you for an unlock code with a non tmobile or non tmobile mnvo sim then youre are unlocked.
10. Odin 4.3 or 4.4 and youre done
Click to expand...
Click to collapse
Some additional info:
blu422 said:
This method works the only problem I encountered is while flashing the modem i couldn't make it flash, i would flash it but then in settings my baseband would stay mk2 so the way to fix this is to flash in odin with auto reboot off. then when its done flashing unplug the phone then pull the battery and boot straight into download mode and flash the modem.bin once again same drill, auto reboot off then pull the battery then reboot and it should work.
edit: just kidding this method did not work for me, the unlock prompt no longer shows up, but an at&t sim card still will not work, although it does tell me i have five voicemails that i cannot listen to. no texts no calls no data, where it should say at&t in the notification panel it says no service... :/ any ideas? I havent yet updated back to 4.3/4.4 yet could that be the problem?
when I try to call it just says "not registered on network"
turns out that it is just because i havent updated back yet, not even a t-mobile sim works. turns out I have a blacklisted imei! but i think I am unlocked hopefully this (at least the first part) answers a few questions aroused during this process, may be the op could get updated with a couple key peices in this post. also huge kudos for this!
Click to expand...
Click to collapse
hello,
i tried to flash the stock tar as you said, but i get an error.
it says:
write protection: enable
secure magiccode check fail : boot
what can i do in this case?
thank you!
ionutul said:
hello,
i tried to flash the stock tar as you said, but i get an error.
it says:
write protection: enable
secure magiccode check fail : boot
what can i do in this case?
thank you!
Click to expand...
Click to collapse
I'm not too sure actually, I didn't run into that error, and I don't have other S4s I can try it out on.
There were several things I did do before trying to flash back though, that may have had an effect. The first is rooting through motochopper's method. The second was installing and running regionlock away. Try rooting first and then flashing. Otherwise, I might have to chalk it up as something unique with my phone I'm not aware of.
Tsumi said:
After several hours of trial and error, I found a way that worked for me. It will trip the Knox counter though. Also, what worked for me may not work for everyone else. If you brick your device that's not my fault in any way, so good luck
Using this guide, flash back to the stock TAR (not the UVUAMDL TAR). This restores 4.2.2, which allows access to the menu. However, this alone is not enough, as it won't give you access to the perso functions. Attempting to flash the UVUAMDL TAR will result in an error (at least, it did for me).
Second, extract the modem.bin from the UVUAMDL file, and flashed it to the phone using Odin. It's similar to the guide above, but instead of using PDA, you use phone. This gives you access to the perso functions, as it forces the baseband back to UVUAMDL from UVUEMK2. It may be possible to flash the UVUAMDL.tar modem files found in other threads, I haven't tried this out myself though.
Now, at this point you can follow the instructions in this thread, as every option should now be available. If they're not, make sure your Android version is 4.2.2 and that the baseband is UVUAMDL.
If it works at this point, great, go on to the next step (you may have noticed by now that your sound is not working). If not, use RegionLock Away to fully unlock the phone. At this point, your phone should be fully unlocked and you can see it connected to the network. However, dialing/calling lags significantly, and there is no sound.
The next step is to use Odin to fully restore UVUEMK2, which would restore full functionality. You can download the file from here, and flash using the same steps above. This will restore full sound and phone functionality, while your device remains unlocked. If it gets stuck during the boot animation, you simply need to do a factory wipe from recovery (not sure if this works, haven't tested it myself), or just install your recovery of choice from Odin and install whatever ROM you want to use (what I did, which still required a full factory reset from recovery). Skipping restoring UVUEMK2 and installing your ROM of choice does not work, however. You will still have no sound and the phone function will lag considerably.
If everything goes well, you should have a fully unlocked T-mobile Galaxy S4.
Click to expand...
Click to collapse
HELP...!
Ok, I've been reading many many articles for the past few days and finally have mustered enough energy to attempt the unlock my T-Mobile SGH-M919 running MK2 firmware. Since I was unable to get into the service menu and input keys using the many directions on this site.... I attempt to flash to old older firmware, following this guide.
I followed each direction 1 step at and time and followed it to the "T". Anyway, long story short... I tried and it soft bricked my phone. I get the warning screen that the firmware was unsuccessful and that I need to run recovery using Samsung Kies. I download the software and attempt recovery. It got to roughly 90% and then it failed too. I reverted back to Odin and reflash using MK2. It too got to about 90% and fails. What is going on?
Any more tips to get this thing working again?? Help.
Got to only 93% via Kies... two times!
Um I'm almost sure once you are on mk2 your not able to go back to mdl. Do to the boot loader...
Sent from my SGH-M919 using xda app-developers app
---------- Post added at 08:52 PM ---------- Previous post was at 08:51 PM ----------
If your rooted you can try region Loa away by chain fire see if it works.
Sent from my SGH-M919 using xda app-developers app
egren58 said:
Um I'm almost sure once you are on mk2 your not able to go back to mdl. Do to the boot loader...
Sent from my SGH-M919 using xda app-developers app
---------- Post added at 08:52 PM ---------- Previous post was at 08:51 PM ----------
If your rooted you can try region Loa away by chain fire see if it works.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
wwwhheeew.... finally got it to unbrick. Took 4 hours to get this thing operational again. I thought the guide specifically says it can downgrade from MK2 to MDL? I already ran the Regionlock app and it appears to be done right, but it's still not sim unlocked.!
dyangster said:
wwwhheeew.... finally got it to unbrick. Took 4 hours to get this thing operational again. I thought the guide specifically says it can downgrade from MK2 to MDL? I already ran the Regionlock app and it appears to be done right, but it's still not sim unlocked.!
Click to expand...
Click to collapse
same problem, RLA does not work on MK2, flashing MDL modem and going through the motions also does NOT sim unlock...cant seem to get this thing working.
funny thing is it wont even register on the network with a GoSmart sim, GoSmart being a TMO MVNO.
i hate sammy...
I flashed to the stock firmware first, which I believe is the MDB firmware. It doesn't work attempting to go to MDL. Going to MDB gets you 4.2.2, but you would still be locked because it keeps the MK2 modem.
The second step was to extract the MDL modem.bin from the TAR, and then flash that on Odin via the phone method. That was how I was able to downgrade the modem from MK2 to MDL, but that screws up sound, but allows you access to the unlock functions.
Odin MDB and factrory reset in recovery. I was stuck at "Kernel is not seandroid enforcing set warranty bit: Kernel" at the boot up screen. I thought it didnt work and wasnt going to boot up and was looking MK2 tar and then out of nowhere after 5 mins I hear the tmobile boot up sound and this **** actually boot it. Im in MDB 4.2.2 with mk2 baseband. Just need to downgrade baseband and Ill let you know if it works guys. Ill post all files as well that I use
---------- Post added at 10:34 PM ---------- Previous post was at 10:07 PM ----------
I have successfully unlocked and I was at 4.3. Huge props to Tsumi. Ill post an updated guide of Tsumi unlocked method of all the files I used
---------- Post added at 10:58 PM ---------- Previous post was at 10:34 PM ----------
How to Unlocked M919 on MK2 4.3. This method has no been tested on the new MB4 4.4.2 update
Huge Props to Tsumi. Is his method and thank/donate to him. i use his guide but it wasnt clear enough so I went searching to internet for links for all the correct files.
Im not responsible for any bricks but if you follow carefully then you shouldn't
This method will trip KNOX
1. Download MDB Tar. Extract from 7zip file and then rename the file (remove the .md5) so the filename should be "SGH-M919-UVUAMDB-k0nane.tar"
http://www.hunterspad.com/Domains/S...ir=Xda/Galaxy+S4/T-Mobile+S4/Return+To+stock/
2. Odin the MDB Tar in the PDA slot and once it finish go to recovery and factory reset.
3. It will take forever to reboot and it will be stuck at the boot up screen for awhile with this error "Kernel is not seandroid enforcing set warranty bit: Kernel". In about to 5-10 mins it will boot up.
4. Now youre in MDB 4.2.2 with MK2 modem.
5. Odin the .bin file below. Use the PHONE slot in odin and not PDA. Again it will take 5-10 mins to boot up with the error "Kernel is not seandroid enforcing set warranty bit: Kernel"
https://mega.co.nz/#!S9AjUAYA!GOOIp2B4z5dIZy2RFxwQBsMz_v7nRJiOypoAjkuAwtc
6. Now you have MDB Rom with MDL modem
7.Odin CF AutoRoot with the link below in the PDA Slot. It will take 5-10 mins to boot up with the error "Kernel is not seandroid enforcing set warranty bit: Kernel"
http://download.chainfire.eu/328/CF-Root/CF-Auto-Root/CF-Auto-Root-jfltetmo-jfltetmo-sghm919.zip
8.Download RegionLock Away 1.3 App either in the thread below or buy it at the google play store to support the developer
http://forum.xda-developers.com/showthread.php?t=2470551
9. Run RegionLock Away and click reboot now. It will take another 5-10 mins to boot up and if you dont ask you for an unlock code with a non tmobile or non tmobile mnvo sim then youre are unlocked.
10. Odin 4.3 or 4.4 and youre done
ionutul said:
hello,
i tried to flash the stock tar as you said, but i get an error.
it says:
write protection: enable
secure magiccode check fail : boot
what can i do in this case?
thank you!
Click to expand...
Click to collapse
I'm curious, how come you didn't trip the Knox counter?
Help
Hey I Have A Tmobile Galaxy s4 and it says my sim isn't registered on the network i was just wondering if there was anyway to get this running, i tried the above method and it completed but i still can't use a tmobile sim on my phone.
JerkLife said:
Hey I Have A Tmobile Galaxy s4 and it says my sim isn't registered on the network i was just wondering if there was anyway to get this running, i tried the above method and it completed but i still can't use a tmobile sim on my phone.
Click to expand...
Click to collapse
If you have a T-mobile S4 and a T-mobile sim, and it says sim is not valid, then you need to contact T-mobile about your sim card. Either that, or your phone has a bad IMEI (not sure what error message would pop up if you have a bad IMEI). Either way, it's not an unlocking problem. Either your sim or your phone is invalid on the T-mobile network.
This method works the only problem I encountered is while flashing the modem i couldn't make it flash, i would flash it but then in settings my baseband would stay mk2 so the way to fix this is to flash in odin with auto reboot off. then when its done flashing unplug the phone then pull the battery and boot straight into download mode and flash the modem.bin once again same drill, auto reboot off then pull the battery then reboot and it should work.
edit: just kidding this method did not work for me, the unlock prompt no longer shows up, but an at&t sim card still will not work, although it does tell me i have five voicemails that i cannot listen to. no texts no calls no data, where it should say at&t in the notification panel it says no service... :/ any ideas? I havent yet updated back to 4.3/4.4 yet could that be the problem?
when I try to call it just says "not registered on network"
turns out that it is just because i havent updated back yet, not even a t-mobile sim works. turns out I have a blacklisted imei! but i think I am unlocked hopefully this (at least the first part) answers a few questions aroused during this process, may be the op could get updated with a couple key peices in this post. also huge kudos for this!
blu422 said:
This method works the only problem I encountered is while flashing the modem i couldn't make it flash, i would flash it but then in settings my baseband would stay mk2 so the way to fix this is to flash in odin with auto reboot off. then when its done flashing unplug the phone then pull the battery and boot straight into download mode and flash the modem.bin once again same drill, auto reboot off then pull the battery then reboot and it should work.
edit: just kidding this method did not work for me, the unlock prompt no longer shows up, but an at&t sim card still will not work, although it does tell me i have five voicemails that i cannot listen to. no texts no calls no data, where it should say at&t in the notification panel it says no service... :/ any ideas? I havent yet updated back to 4.3/4.4 yet could that be the problem?
when I try to call it just says "not registered on network"
turns out that it is just because i havent updated back yet, not even a t-mobile sim works. turns out I have a blacklisted imei! but i think I am unlocked hopefully this (at least the first part) answers a few questions aroused during this process, may be the op could get updated with a couple key peices in this post. also huge kudos for this!
Click to expand...
Click to collapse
As I have only done this on one phone, I am not sure what issues you were encountering. Also, like I said in my post, YMMV, different phones may behave differently.
What do you want to see updated?
wrong
the 2nd link is not a link to the files. it's a link to internet browsers..
BoloVon said:
the 2nd link is not a link to the files. it's a link to internet browsers..
Click to expand...
Click to collapse
All links are working for me...
Tsumi said:
As I have only done this on one phone, I am not sure what issues you were encountering. Also, like I said in my post, YMMV, different phones may behave differently.
What do you want to see updated?
Click to expand...
Click to collapse
That message pops up when its blacklisted so it won't work regardless if you unlock it
Sent from my SGH-M919 using Tapatalk
No wifi
i was able to flash stock tar to my s4. now i cannot get wifi to work.. i tried turning it on but the signal comes back off.
help please..
Tsumi said:
What do you want to see updated?
Click to expand...
Click to collapse
That \/ maybe just add a link to my post saying if you have problems with the .bin part then see here or not its whatever you see fit
blu422 said:
the way to fix this is to flash in odin with auto reboot off. then when its done flashing unplug the phone then pull the battery and boot straight into download mode and flash the modem.bin once again same drill, auto reboot off then pull the battery then reboot and it should work.
Click to expand...
Click to collapse
---------- Post added at 10:17 PM ---------- Previous post was at 09:52 PM ----------
BoloVon said:
i was able to flash stock tar to my s4. now i cannot get wifi to work.. i tried turning it on but the signal comes back off.
help please..
Click to expand...
Click to collapse
Which stock are you referring to? The 4.4.2 one?
Hi. I am encountering problems after installing this CWM-based Recovery v6.0.4.4
I admit, I am a noob regarding this.
Going back, the phone can access The CWM-based recovery by pressing the power button and volume up, can use menus, advanced menu,
I wiped the partition and cleared cache and dalvik cache but when you restart, screen stops at LG logo and (Secure booting error, Cause: boot certification verify) text is displayed.
I know I was unsure of everything and flashing androids are new to me especially on my device.
can I unlock the bootloader even with the CWM-based recovery alone?
Model name: F240S
android version. 4.4.2
I'm having a similar problem. I have CWM from Freegee on my phone.
Last night, when I was unable to flash either or two different roms, I decided to check for an OTA update. The phone downloaded it, and when it was finished, it went into looping into recovery. I then decided to factory reset, wipe data.. still phone goes back to recovery. Then I decided to just use the backup I had made earlier in CWM. Still stuck in recovery loop.
Anyone? Anyone?
Perry2547 said:
I'm having a similar problem. I have CWM from Freegee on my phone.
Last night, when I was unable to flash either or two different roms, I decided to check for an OTA update. The phone downloaded it, and when it was finished, it went into looping into recovery. I then decided to factory reset, wipe data.. still phone goes back to recovery. Then I decided to just use the backup I had made earlier in CWM. Still stuck in recovery loop.
Anyone? Anyone?
Click to expand...
Click to collapse
You can't install an OTA update with a custom recovery. It needs the stock recovery. Time to familiarize yourself with the TOT method of flashing back to stock
Sent from my LG-E980 using XDA Free mobile app
thathamiam said:
You can't install an OTA update with a custom recovery. It needs the stock recovery. Time to familiarize yourself with the TOT method of flashing back to stock
Sent from my LG-E980 using XDA Free mobile app
Click to expand...
Click to collapse
I just did some more searching. I'm coming up with stuff like "install the lg flash tool" , "and if that doesn't work, install (If you cannot run LGFlashTool2014.exe, please install Visual C++ Runtime Library) - VC_RedistInstaller.exe - 47.7 Mb"
HOLY PHUCKING HELL! WHAT DO I HAVE TO DO? Go get a phucking degree from MIT to just to use my phucking fone???
Seriously. Someone on this site needs to learn how to teach. I know that there are men here with IQs in the upper range of 140 plus.. but they can't teach. sad sad sad.
I've been going at this for so long now. My computer is littered with downloaded files. And then the phone I had before this it was like, hmmm, I'll flash a cyanogenmod rom because they under stand the common man. WRONG. Their mods suck battery life more than stock roms. Okay, I'll flash Carbon rom... not any better, devs have purposely darkened the screen to make it look like battery life is better.. I tried rom after rom after rom. They all have problems. NOt just minor problems either.
Android is the punk in prison that gets passed about by the violent inmates. First Samsung has his way with Android, then Google gets in on the gangbang and then Verizon or AT&T gets sloppy thirds..
I have an e980 and this method had been flawless multiple times. As far as battery life, that all depends on 100 different things, but I always flash madmack's modem, then wipe cache and dalvik. Deep sleep is pretty much guaranteed after that.
Edit: forgot the link for the back to stock method http://forum.xda-developers.com/showthread.php?t=2302660
Sent from my LG-E980 using XDA Free mobile app
I searched for a day or two from the forums and they said that there are no unlocked bootloader for 4.4.2 OTA yet.
so sad.
What i did was I used the LG mobile support tool and my phone went back to stock.
my device is also unsupported on Freegee and on CWM, my device isn't available.
fafalafafa said:
I searched for a day or two from the forums and they said that there are no unlocked bootloader for 4.4.2 OTA yet.
so sad.
What i did was I used the LG mobile support tool and my phone went back to stock.
my device is also unsupported on Freegee and on CWM, my device isn't available.
Click to expand...
Click to collapse
There has never been an unlocked bootloader for the OGP
Sent from my LG-E980 using XDA Free mobile app
Perry2547 said:
I just did some more searching. I'm coming up with stuff like "install the lg flash tool" , "and if that doesn't work, install (If you cannot run LGFlashTool2014.exe, please install Visual C++ Runtime Library) - VC_RedistInstaller.exe - 47.7 Mb"
HOLY PHUCKING HELL! WHAT DO I HAVE TO DO? Go get a phucking degree from MIT to just to use my phucking fone???
Seriously. Someone on this site needs to learn how to teach. I know that there are men here with IQs in the upper range of 140 plus.. but they can't teach. sad sad sad.
I've been going at this for so long now. My computer is littered with downloaded files. And then the phone I had before this it was like, hmmm, I'll flash a cyanogenmod rom because they under stand the common man. WRONG. Their mods suck battery life more than stock roms. Okay, I'll flash Carbon rom... not any better, devs have purposely darkened the screen to make it look like battery life is better.. I tried rom after rom after rom. They all have problems. NOt just minor problems either.
Android is the punk in prison that gets passed about by the violent inmates. First Samsung has his way with Android, then Google gets in on the gangbang and then Verizon or AT&T gets sloppy thirds..
Click to expand...
Click to collapse
Your dramatized posts between threads show you are having a hard time. A person does not need a degree to flash, just the patience to read a lot on a forum like xda regarding their phone and android in general.
People only notice something like battery life on a given rom due to the presence of other options they can compare it to. Apple, for example, is just one thing. One ios iteration having a better something over the other is irrelevant as there is nothing to apply degrees of comparison to. Then, hardware variety, etc.
Some of the points you are upset about in the process of flashing could be resolved by a google search or xda forum search.
Sent from my LG-E980 using XDA Premium 4 mobile app
Well I finally got it working.
What one has to do to get roms flashed is to use madmacks's term. And when you're on recovery mode, you must toggle Loki support to disabled or the install of the new Rom will abort.
Unfortunately, Camera has stopped.
---------- Post added at 01:59 PM ---------- Previous post was at 01:57 PM ----------
For the record, I did search. And search. And search.
The problem here at xda is that many of the developers are so smart that they are unable to articulate down to us regular people.
Unfortunately, Camera has stopped.
Perry2547 said:
Well I finally got it working.
What one has to do to get roms flashed is to use madmacks's term. And when you're on recovery mode, you must toggle Loki support to disabled or the install of the new Rom will abort.
Unfortunately, Camera has stopped.
---------- Post added at 01:59 PM ---------- Previous post was at 01:57 PM ----------
For the record, I did search. And search. And search.
The problem here at xda is that many of the developers are so smart that they are unable to articulate down to us regular people.
Unfortunately, Camera has stopped.
Click to expand...
Click to collapse
Cool. Glad to hear it worked.
Sent from my LG-E980 using XDA Premium 4 mobile app
Should I move this question to another post?
I have another problem. my phone just got no signal and says "Service disabled". on the notification bar it just loads and says "Searching for networks". it never found any networks. I switched the same SIM to another phone and it has a signal. the problem happened after I edited the build.prop and changed the ro.build.local from "KR" to "US" just to remove the dual clock from the lockscreen (because F240 has a dual clock which is non-removable except if you use the sqlite editor but that method did not work for me. the editor closes and says "*programname* has closed unexpectedly").
I made a factory reset and still there is no signal. I'm using stock kitkat firmware from LG and not rooted. can you help me with this one?
Thanks
Have you checked your apn settings?
Unfortunately, Camera has stopped.
No, I don't have APNs listed.
but, I was able to install sphinx rom and now the phone always says "unfortunately, com.android.keyguard has stopped" and the phone app was gone, APN settings also gone, call logs gone,
For a short while, I didn't think I had apn's listed but I was not looking in the right place.
Perry2547 said:
For a short while, I didn't think I had apn's listed but I was not looking in the right place.
Click to expand...
Click to collapse
Probably no baseband or null baseband, my suggestion, flash stock through flashtool, if you have free gees made an efs folder you can always restore that too, but i think flashing stock would solve the baseband problem, if that doesnt, there is an online flashing method, that can help
dante_67 said:
Probably no baseband or null baseband, my suggestion, flash stock through flashtool, if you have free gees made an efs folder you can always restore that too, but i think flashing stock would solve the baseband problem, if that doesnt, there is an online flashing method, that can help
Click to expand...
Click to collapse
I don't know about the flash stock through flashtool. I use mobile support tool which I did last night and it was a success. "com.android.phone has closed unexpectedly" or something like that does not appear now on SETTINGS>Tethering & Networks>Mobile Networks OR T Roaming>Select roaming network. because before I'm encountering if I go there.
one last thing is that everything is now stock but still I don't get the signal. unlike before. the signal goes back automatically.
about basebands, I do have a baseband. same as before and I still have my IMEI intact.
That is strange, there is a thread of hyelton, in general section, get the lg flash tool from there, and try to flash the appropriate tot file, if you flash the tot or kdz file for other model, this might result in loss of network
--- Mods, didn't want to post in Android Development and clutter that section, thought General would be a bit better. My deepest apologies if I'm yet in the wrong section, just move it and tell me. Thank you. ---
Alright guys, tried to do some searching on this topic - no help found. So i'm resorting to what I hate to do, flooding the forums with more topics. Little bit of background to help troubleshoot, I've been rooting and rom-ing for about 4 years now with all Verizon Samsung phones (locked bootloaders and all that fun stuff) but just switched to sprint recently and having a few issues with roms.
On to my issue...
My phone has been experiencing a bunch of lag lately. So bad where the phone locks up for about 5 to 7 seconds about 3-4 times an hour and it is getting annoying as it's locking it at some crucial points. So, I have TWRP on there, rooted on stock 4.4 and tried to flash CM12 nightlies for this phone (the Sprint version). TWRP refused to install it, saying that the phone itself was the trlteTMO version and couldn't flash the trlteSPR roms. I flashed the TMO CM12 nightly and it flashed perfectly fine, but my service didn't work. I believe I got 3G/LTE and calling (unsure, can't confirm.) But no texts went through. But what the great part was, is that it did not stutter and Lollipop was absolutely f-in' gorgeous. So i'm assuming the phone accepted the software, but the radios weren't correct. I loved CM12 so much, but I use XPOSED for a few things. (Basically just Keepchat), So i'm okay with going to CM12 if someone can get my Sprint phone, which i got through Sprint, to work with Sprint roms. I'm at a brick wall.
Mind you that I have access to a windows computer, but it's junk and would rather flash using ODIN PRO on my phone, or just using my recovery. I use a Macbook Pro as my daily, but I can't get heimdall to work as i once did on my S3. I can't even find support or any downloads for it. So, i'm pretty much back to noob status and just need some good guidance. Thank you for reading, and help me flash something new!
Did you use the correct recovery for spr? Is only thing I can think of.... Maybe you flashed the tmo recovery
spleef said:
Did you use the correct recovery for spr? Is only thing I can think of.... Maybe you flashed the tmo recovery
Click to expand...
Click to collapse
Definitely checking that. Sounds like it could be a very good reason for it to reject the tar.
Branski81 said:
Definitely checking that. Sounds like it could be a very good reason for it to reject the tar.
Click to expand...
Click to collapse
Using a .tar file in recovery could be your 1st problem....
Sent from my SM-N910P using Tapatalk
I agree with spleef. There's no other reason I can think of that would cause TWRP recovery to not install a sprint rom and give you that error message. You should really double check the tar files bwhen downloading them and definitely before flashing them with odin. Another thing, you are very brave for knowlingly flashing a T-Mobile rom on your Sprint phone. Seriously, you might want to Odin back to the stock. Sprint NK2 rom .tar and startb over fresh. It would be in your best interest at this point.
BigJPNut said:
Using a .tar file in recovery could be your 1st problem....
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Excuse me, you're right. The recovery file was not tar. You're correct though, that does seem as it would just a littttttle bit of an issue..
---------- Post added at 12:15 AM ---------- Previous post was at 12:11 AM ----------
tx_dbs_tx said:
I agree with spleef. There's no other reason I can think of that would cause TWRP recovery to not install a sprint rom and give you that error message. You should really double check the tar files bwhen downloading them and definitely before flashing them with odin. Another thing, you are very brave for knowlingly flashing a T-Mobile rom on your Sprint phone. Seriously, you might want to Odin back to the stock. Sprint NK2 rom .tar and startb over fresh. It would be in your best interest at this point.
Click to expand...
Click to collapse
I cannot fully confirm that it was the wrong TWRP as the only recoveries I had on my computer and phone storage were sprint versions.
I did however reinstall the sprint recovery again after having to flash back to stock due to a random bootloop issue. So after reflashing 4.4 stock, reinstalling the recovery and restoring to a previous backup, I am now clean flashed on 5.0.2 all cellular features working on CM12 Official.
Mods, if you could please close or delete this thread, that would be appreciated.
Thank you @spleef, I'm sure you were correct anyways.
/end
[email protected]
I feel your pian. Same somewhat similar happend to me on the Snapdragon S5.
I did a factory reset. Hook up to Kies3. Upgraded to NK2. Did a little Coding.Wiated for Lolipop to role out Official. Rooted debloated N knox free. Found in General tips and tricks.
All OS is running Super Fast-