I successfully unrooted my phone but it still shows up as modified. I'm wondering what I did wrong and if there's another way to go about it. Here's what I did.
Used Triangle Away to reset my binary. It said it was successful and shows my count as "0". Then I downloaded the Bell stock firmware for my phone, sgh-i747m. The md5 checked out. I then tried flashing using mobile odin. Still shows as modified. I then tried it all again with pc version of Odin. Everything boots up. I was unrooted and even though I reset my binary I'm seeing "modified" under settings/status.
Has anyone encountered this before? Any work arounds?
Sent from my SGH-I747M using xda app-developers app
marocca said:
I successfully unrooted my phone but it still shows up as modified. I'm wondering what I did wrong and if there's another way to go about it. Here's what I did.
Used Triangle Away to reset my binary. It said it was successful and shows my count as "0". Then I downloaded the Bell stock firmware for my phone, sgh-i747m. The md5 checked out. I then tried flashing using mobile odin. Still shows as modified. I then tried it all again with pc version of Odin. Everything boots up. I was unrooted and even though I reset my binary I'm seeing "modified" under settings/status.
Has anyone encountered this before? Any work arounds?
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
A little search would've gave you your answer. Simply factory reset and it won't show ''modified'' anymore.
*Know that it will clear all your data*
BWolf56 said:
A little search would've gave you your answer. Simply factory reset and it won't show ''modified'' anymore.
*Know that it will clear all your data*
Click to expand...
Click to collapse
I guess I needed a little "more" searching but thanks a lot for the info!
Sent from my SGH-I747M using xda app-developers app
BWolf56 said:
A little search would've gave you your answer. Simply factory reset and it won't show ''modified'' anymore.
*Know that it will clear all your data*
Click to expand...
Click to collapse
So I did it all again and did the factory reset. Still modified.
Sent from my SGH-I747M using xda app-developers app
marocca said:
So I did it all again and did the factory reset. Still modified.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Mind if I ask why you don't want it to show modified?
Also, little clarification: by flashing 4.1.1 (stock), you will get the modified status.
BWolf56 said:
Mind if I ask why you don't want it to show modified?
Also, little clarification: by flashing 4.1.1 (stock), you will get the modified status.
Click to expand...
Click to collapse
I fully admit to being a noob, but it seems that when I try to check for updates on my phone it gives me a message saying that my device has been modified and updates are not available for it. I've been spent months flashing and trying out different ROMS and just wanted to revert fully back to stock for a bit. I love using Bluetooth Audio streaming and have never had as good of audio quality as I did with stock. I understand that playing around with drivers and kernels could help that with custom rom but until i'm more knowledgeable about that kind of stuff I didn't want to flash anything.
Just before I checked this message I realized that I've been flashing 4.1.1 stock and figured that's where my problem lies. Currently downloading stock ICS for Bell.
Thanks again!!
marocca said:
I fully admit to being a noob, but it seems that when I try to check for updates on my phone it gives me a message saying that my device has been modified and updates are not available for it. I've been spent months flashing and trying out different ROMS and just wanted to revert fully back to stock for a bit. I love using Bluetooth Audio streaming and have never had as good of audio quality as I did with stock. I understand that playing around with drivers and kernels could help that with custom rom but until i'm more knowledgeable about that kind of stuff I didn't want to flash anything.
Just before I checked this message I realized that I've been flashing 4.1.1 stock and figured that's where my problem lies. Currently downloading stock ICS for Bell.
Thanks again!!
Click to expand...
Click to collapse
If you want a ROM that has working BT streaming, try Task's AOKP.
BWolf56 said:
If you want a ROM that has working BT streaming, try Task's AOKP.
Click to expand...
Click to collapse
I love Task's AOKP. It's the one I always returned to and used the most, but with any rom I tried the BT audio always had a bit of clipping/overdrive. I tried adjusting my volume levels but it wouldn't go away. I never tried other kernels, modems or drivers and suspect that the solution to that problem could be found in one of those, but like I stated above, I'm not knowledgeable enough yet. Wouldn't feel confident messing around with kernels and modems. And I always seemed to be on the modem intended for Bell users.
Here is what I did, this was on a Note 2, flashed back to stock rooted, ran triangle away, uninstalled superuser then flashed a stock rom without root. It may be the long away to the end but it worked.
I ended up getting it to work. Flashed stock ICS then upgraded to Jelly Bean.
Sent from my SGH-I747M using xda app-developers app
Related
OK, so here is my deal. I got my SGS2 a little over a year ago. With the help of this forum I was able to root without issue and flash many of roms. I am now at a point in my playing around that I am having issues doing anything. I would like to just factory reset in Kies, but I can't even do that. For some reason (I have a telus phone), Kies thinks I am a T-Mobile phone, or at least its what I can tell. When I launch Kies and it displays the phone and the and its settings eg: PDA, Radio, etc they all say TMB. I have no idea if that has nything to do with it or not. I tried flashing the Telus radio via Odin, though nothing changed in Kies. The last ROM I used seemed to have screw my Clock Work Recovery and I cannot figure how to get it back. I have tried re-flashing CWR, but I don't think I really understand the difference between Touch and Touch-less. As you can see I am fairly lost at this point. I am turning to all of you for help. I am open to trying anything, just point me to some guides, tips, tricks. I have tried a ton of stuff with no luck. I know these questions get asked all the time and I apologize for making another. I would not be doing so unless I really needed the help as usually I am pretty good with this stuff. I appreciate everyone in this forums and all the time they have put in to bringing us great information. I am thankful to anyone that can help me out. If you need any further info please just ask and I'll provide it as fast as I can!
Have you tried flashing the stock Rom with Odin?
Sent from my SGH-I727 using xda app-developers app
jd1639 said:
Have you tried flashing the stock Rom with Odin?
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I have, actually I may be running it now actually. It just seems like I have a lot of over lapping stuff. Things that were not fully removed, parts left behind, etc. Is there a easy way to lock up what ROM is running. I assume it's the stock rom as I have the Samsung Apps application on my phone and that is removed with most custom roms. Like I said I really just want to nuke this biatch and start from step one again. She is running like crap atm.
If you flashed the stock Rom you won't have cwm any more. You'll have to reflash it. The phone will be like it was when it was new.
You can get the stock Rom from Sammobile.com for your device and carrier. You 'll have to extract the tar.md5 file out of it using 7_zip. Then flash it with Odin
Sent from my SGH-I727 using xda app-developers app
jd1639 said:
If you flashed the stock Rom you won't have cwm any more. You'll have to reflash it. The phone will be like it was when it was new.
You can get the stock Rom from Sammobile.com for your device and carrier. You 'll have to extract the tar.md5 file out of it using 7_zip. Then flash it with Odin
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I think the reason I am confused is if it worked, which it appears that it did why does it retain all my data? I would just like to totally kill the ***** to nothing. I'll try flashing to stock again with the site you provided when I get. I appreciate your help!
When you say kill it, do you want to make it so it never works again?
Sent from my SGH-I727 using xda app-developers app
jd1639 said:
When you say kill it, do you want to make it so it never works again?
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Nah, I meant just no data totally factory. Which last night I did figure out how to do finally. I think I just had a lot of messed up info, wrong files etc. I also think my permissions were totally messed on my phone. Anyways I got it all sorted. Thank you!
Sounds good, don't forget the thanks button.
Sent from my SGH-I727 using xda app-developers app
if that doesnt work, follow these steps. easy as pie?
http://forum.xda-developers.com/showthread.php?t=1513359
I first posted this in MrRobinson's excellent thread at http://forum.xda-developers.com/showpost.php?p=35165945&postcount=1610, but decided others might benefit from it that may not be following his instructions because they're already rooted...
For now, just see my instructions in the post mentioned above. Once I get off work this evening I will be updating this post with more detailed information. At least one other user has followed these instructions and reported that his flash counter remains at 0, even after multiple reboots and custom recovery actions.
The usual disclaimers about bricking your phone, blowing up your grandmother's house, drowning your dog, etc. apply. I'M NOT RESPONSIBLE!!!
Reserved - just in case...
I can confirm this method works as described. I also added instructions in the same thread on how you can still use this method if you happen to have already upgraded to JB via the traditional method (ie via ODIN or Kies) and have a count or custom status. It requires reverting to stock ICS and recovery and then moving forward with the above process, and the end result is Rooted JB with Custom Recovery and retaining official rom status with no counter increments.
whats the point.. if you put a custom recovery on it updates the counter anyway.. on every boot. unless you root and remove certain files.. and if you are rooted and remove those. you can use triangle away anway.
If you revert to ics, then flash jb without the accompanying bootloaders you don't have to worry the flash counter. Why is that important? In case you need to warranty it and can't get to triangle away to reset it. And some of us like to say its never been tripped
Btw, I'm running rooted stock with twrp and my counter is still 0. And i installed twrp after flashing jb.
lgkahn said:
whats the point.. if you put a custom recovery on it updates the counter anyway.. on every boot. unless you root and remove certain files.. and if you are rooted and remove those. you can use triangle away anway.
Click to expand...
Click to collapse
That's the point. I flashed and KEPT my custom recovery, and it does not increase the counter no matter how often I use it. I haven't tried loading a different custom recovery now that I'm on JB, but so far all is well.
By the way, sorry I haven't followed up on the OP. Been very busy.
78Staff said:
I can confirm this method works as described. I also added instructions in the same thread on how you can still use this method if you happen to have already upgraded to JB via the traditional method (ie via ODIN or Kies) and have a count or custom status. It requires reverting to stock ICS and recovery and then moving forward with the above process, and the end result is Rooted JB with Custom Recovery and retaining official rom status with no counter increments.
Click to expand...
Click to collapse
Thanks for the other post. I was beginning to think no one even cared. I'll see if I can incorporate your info into the OP when I finally get around to it...
lgkahn said:
whats the point.. if you put a custom recovery on it updates the counter anyway.. on every boot. unless you root and remove certain files.. and if you are rooted and remove those. you can use triangle away anway.
Click to expand...
Click to collapse
You're doing it wrong. Mine still displays 0 and official after installing multiple recoveries, countless zip flashes to include AOKP and TW ROMs and approx 4-5 Odin flashes. My wife's recently rooted and jb'd S3 also says the same thing.
Sent from my SAMSUNG-SGH-I747 using xda premium
Are any of you having SD card issues with the stock version of JB?
LAKsupply said:
Are any of you having SD card issues with the stock version of JB?
Click to expand...
Click to collapse
Nope. Have you tried reverting to ICS to see if the problem persists?
Sent from my SAMSUNG-SGH-I747 using xda premium
d3athsd00r said:
You're doing it wrong. Mine still displays 0 and official after installing multiple recoveries, countless zip flashes to include AOKP and TW ROMs and approx 4-5 Odin flashes. My wife's recently rooted and jb'd S3 also says the same thing.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
no that is becuase one of the flashes you did removed those recovery files that comes with stock jb.. or replaced the kernel that reflashes them..
normal upgrade from ics to stock jb.. will reset counter on every boot unless you change the kernel or remove the recovery image.
d3athsd00r said:
Nope. Have you tried reverting to ICS to see if the problem persists?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
It's fine on ICS... this is Jedi Invasion JB and the KT747 kernel. I wasn't sure if it was just the ROM and then noticed that others with different roms and stock roms had the same issues. I'm wondering if it wasn't an issue in the initial JB release (this is a ported T Mobile rom) that the dev built this rom off of. I'll flash another JB version and see if the problem persists.
lgkahn said:
no that is becuase one of the flashes you did removed those recovery files that comes with stock jb.. or replaced the kernel that reflashes them..
normal upgrade from ics to stock jb.. will reset counter on every boot unless you change the kernel or remove the recovery image.
Click to expand...
Click to collapse
I.E. I did it right. Doing it right the first time keeps you from having to fix it later.
Sent from my SAMSUNG-SGH-I747 using xda premium
So... it appears my previous issue was a bad sd card. It's kind of a big coincidence that the old card didn't work with the Jedi rom, and now the new card doesn't work with any rom. I just flashed AOKP and the correct KT747 kernel, and no love. I pulled the 32g sd card and fed it my wife's old 8g card, and it works perfectly. Is there a such thing as a rom cooking an sd card?
great find! followed the instructions with mobile odin and worked like a charm, I came from a jb aosp rom, but first I nandroid back to an ics-lg1 backup I did a few months back, no counter tripping after a few reboots into recovery
one question, is there any thread where I can find mods for this 4.1 TW stock jelly bean, like power menu, toogles, kill back button,tether etc if anyone has a link please share
many thanks!
When your sdcard went did it say damaged? That happened to me going from ics to jb mr robinsons official stock. So i put in a brand new card, then it tells me under about status is modified which it wasnt when the first sd card worked. Even odder my pc couldnt see the card, so i thought it truly was damaged. I put it back in just to try a day later and all of a sudden i can format it within the phone, which, I due and then it works again and the modified under status is back to normal. Im gonna go through the source of that package this week and see if I can find whats up and what could of tripped and then reverted that counter.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Right on this worked great! And now don't have to worry about the stupid flash counter
sent from the dark side of the universe....
I followed the method in this thread (using mobile odin to go from rooted ICS to rooted JB). It was pretty easy and it worked great. However, after the first restart, I started having a strange problem. Every 5 minutes, the phone will lose its network connection for approximately 30 seconds. This appears as red on the "Mobile network signal" under battery usage details, and I'm unable to make any calls. This drop happens like clockwork. You could set your watch by it.
I've tried everything (uninstalling certain programs, flashed different modems, factory reset, etc) and nothing worked. I reverted back to ICS and then redid the method from this thread, and the same thing happened (JB worked great until I restarted for the first time, etc..
Any ideas? For a while I thought it was some weird issue with the analog clock widget.... But getting rid of that didn't help. And I've tried every possible google search on this issue but I can't find anything. For now I'm back to ICS.
Yea that is weird maybe just try it over again fresh odin ics and go from there. Almost seems like something didn't take going thru the flash process
sent from the dark side of the universe....
did you check the apns? right after I did the flash, it didnt have the "ATT PTA" apn so I had to manually add it
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Hello and thanks to all those before me who give great advice on troubleshooting....
Here's my situation:
Phone is Rooted.
I downloaded an app a few days ago from the Play Store, so I could move my app installs to the sdcard. When i installed the app it said that there was something wrong " can't remember the exact message " and it needed to fix it. My dumbass allowed it to fix it and here is where my problems began.
Right after that I began receiving a message "Shell has been granted Super User", phone began to run sluggish and the Play Store App would always say it was crashing.
So I figured, screw it I would format and start w/a new ROM anyway.... I did not have any sort of backup (of course dumbass)
However I loaded up the latest version of Odin 3.09 and just incase I installed the root.zip again incase that was destroyed. Then I installed the latest version of OUDHS CWM-Based Recovery 1.0.3.3 ( Previously I had TWRP )
I downloaded a few different roms so I could see what I wanted...However...here's where things get interesting, and I did do some research on it but couldn't find a way to resolve the 1st problem.
When I first started to install a ROM, don't remember which one I was getting a signature verification failed....I had read that it could be 2 things, one the MD5 was bad, I verified that, so that wasn't the issue. Then I came across that it may have been a ROM that my device(Samsung) somehow knew wasn't approved, therefore prevented it from being installed....OK fine...
Next I found a ROM that was going to work via installing...So i picked the CM10.2 and wiped/format/davik/cache...etc... Installation took a few mins...Then when I rebooted, it's been on the Cyangenmod screen for 45 mins +....
Is there anyway I can do some verification that something further isn't interfering w/my installs?
Thanks in advance and any guidance is GREATLY appreciated...
Regards
Erik
Odin to stock and try that, always the best choice
Sent from my SGH-M919 using xda app-developers app
aamir123 said:
Odin to stock and try that, always the best choice
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Actually I tried that and I used this one from stockroms.net TMB-M919UVUAMDL-1366964131.zip
the verification failed immediately, however, when I checked it w/the MD5 hash on my computer it checks out...That's where I'm wondering if there is something else going on...
Or are you talking about something else regarding stock? If so could you clarify...Thanks
Use sam mobile.com
And flash the mdl fw from there. Also you may have to unzip the original file to get a tar file
Sent from my SGH-M919 using xda app-developers app
aamir123 said:
Use sam mobile.com
And flash the mdl fw from there. Also you may have to unzip the original file to get a tar file
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Just wanted to say thank you for your help. Both the flashing the recovery back to default and the default ROM worked. Now in the future no more clicking yes when I don't have a backup
Have a great weekend!!
oregongreen said:
Just wanted to say thank you for your help. Both the flashing the recovery back to default and the default ROM worked. Now in the future no more clicking yes when I don't have a backup
Have a great weekend!!
Click to expand...
Click to collapse
glad it worked out for you, I know it can be scary to think you screwed up your phone.
Glad you solved it, ALWAYS MAKE A BACKUP
Sent from my customizable brickable device
mrhughy said:
Glad you solved it, ALWAYS MAKE A BACKUP
Sent from my customizable brickable device
Click to expand...
Click to collapse
This can nvr be said enough.
Hello XDA community, my brother has been having wi-fi and bluetooth issues on his T-MO Note II ever since applying the 4.3 OTA. Before I go on, the first thing I did was use CF-auto root and flash both agni pure stock and devil kernel and neither of them have worked. In addition, I have used dr.ketans patch as well as flashing some AOSP based ROMs such as AOKP and SlimKat and neither of them have yielded any results. I have tried almost everything I can find via XDA and I am truly stumped.
Do you guys have any solutions to the wifi issues? Any help would be greatly appreciated! :good:
Can you elaborate, what wifi issues ?
Frequent disconnects ?
Battery drains ?
Sent from my SGH-T889 using xda app-developers app
Wi-fi wil not turn on whatsoever. I can press the icon to turn it on and it will slide to the on position greyed out, and then go back to off right away. The same for bluetooth as well.
If the phone was already on 4.3 then wifi patch was not needed.
I would advise to flash stock image and start fresh. Make sure to wipe dalvik-cache after flashing stock ROM.
Sent from my SGH-T889 using xda app-developers app
Thanks, I will try that when I can. By any chance do you know where I can find a 4.3 image? I've tried looking into the stickies over at the Dev section and they don't have 4.3 as far as I can recall. The only 4.3 image I see is the stock root injected one from Mr.Robinson.
You can download one from sammobile.com. You will have to register though, make sure you download the file for sgh-t889.
Sent from my SGH-T889 using xda app-developers app
Thank you very much. I will do that tomorrow as I do not have the device with me at the current moment. I will let you know how it goes!
to clarify: http://samsung-updates.com/device/?id=SGH-T889 thats what you need to download
Squilchi said:
to clarify: http://samsung-updates.com/device/?id=SGH-T889 thats what you need to download
Click to expand...
Click to collapse
Ah man, thanks! Unfortunately, I had just finished making an account at SamMobile not too long ago and the download should be finishing up soon. I greatly appreciate the help.
leikamkei said:
Ah man, thanks! Unfortunately, I had just finished making an account at SamMobile not too long ago and the download should be finishing up soon. I greatly appreciate the help.
Click to expand...
Click to collapse
Cool cool just wanted to make sure you got the right tar file. Best of luck
Sent from my N7105 using Tapatalk
I just wanted to say thank you to both ciphercodes and Squilchi for all your help. My brother also says a big thanks as he doesn't have an account here. When the Note II finished rebooting from the image flash via Odin, I almost freaked out because nothing had seemingly changed but then I realized I was already on the 4.3 OTA. I also had an spectacular noob moment by forgetting to wipe cache in stock recovery. After I did that, I am glad to report that Wi-fi and bluetooth work as it's supposed to. I can't say thank you enough. In the odd occasion that this should happen again, a wipe of cache in stock recovery should be okay correct?
leikamkei said:
I just wanted to say thank you to both ciphercodes and Squilchi for all your help. My brother also says a big thanks as he doesn't have an account here. When the Note II finished rebooting from the image flash via Odin, I almost freaked out because nothing had seemingly changed but then I realized I was already on the 4.3 OTA. I also had an spectacular noob moment by forgetting to wipe cache in stock recovery. After I did that, I am glad to report that Wi-fi and bluetooth work as it's supposed to. I can't say thank you enough. In the odd occasion that this should happen again, a wipe of cache in stock recovery should be okay correct?
Click to expand...
Click to collapse
Glad to know issue was resolved. By default it's highly unlikely that these problems will return on a stock ROM but if they do then flashing back to stock is the most optimal solution.
Unfortunately I may have spoken too soon. Wi-Fi was working just fine for a bit but suddenly it can't connect to the network nor see any other networks. It can still turn on but connecting to remembered networks and seeing other networks are a no-go. Bluetooth is wonky as well. I'm starting to think it's hardware but I doubt it.
Sent from my Galaxy Nexus using xda app-developers app
leikamkei said:
Unfortunately I may have spoken too soon. Wi-Fi was working just fine for a bit but suddenly it can't connect to the network nor see any other networks. It can still turn on but connecting to remembered networks and seeing other networks are a no-go. Bluetooth is wonky as well. I'm starting to think it's hardware but I doubt it.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
So close! Hmm it could be hardware I'm not sure either. What are the wifi settings? Also are there any error messages? Did you wipe data after Odin?
Sent from my N7105 using xda app-developers app
I have yet to wipe data since it seemed okay although the notion has been floating in my head. I did wipe cache and shortly after, it didn't work. I suggested unforgetting the network and adding it again and that seemed to work for a little while. No error messages, just the same slide to on greyed out and back to off.
Sent from my Galaxy Nexus using xda app-developers app
leikamkei said:
I have yet to wipe data since it seemed okay although the notion has been floating in my head. I did wipe cache and shortly after, it didn't work. I suggested unforgetting the network and adding it again and that seemed to work for a little while. No error messages, just the same slide to on greyed out and back to off.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Its weird that it was working and now its not wiping data couldnt hurt. Do you have Odin 3.0.9? Flash that tar file again and make sure bootloader update is checked.
Sent from my N7105 using xda app-developers app
Squilchi said:
Its weird that it was working and now its not wiping data couldnt hurt. Do you have Odin 3.0.9? Flash that tar file again and make sure bootloader update is checked.
Sent from my N7105 using xda app-developers app
Click to expand...
Click to collapse
Just a little update, I booted to stock recovery and performed a factory reset and wipe cache partitions but still nothing after it booted. To answer your question, I did use Odin 3.09 and it was already on MK7 prior to my first flash of the tar file in Odin. This is so frustrating.
Sorry for the double post, but I just did a factory reset and wipe cache and just re-flashed the tar file with update bootloader ticked and still a no-go. It's a shame the 4.3 update has borked my brother's Note II to this extent but it seems like the majority of people don't experience this. I'm stumped....
leikamkei said:
Sorry for the double post, but I just did a factory reset and wipe cache and just re-flashed the tar file with update bootloader ticked and still a no-go. It's a shame the 4.3 update has borked my brother's Note II to this extent but it seems like the majority of people don't experience this. I'm stumped....
Click to expand...
Click to collapse
im stumped man... have you tried any custom roms?? flashing mk7 stock kernel?
Squilchi said:
im stumped man... have you tried any custom roms?? flashing mk7 stock kernel?
Click to expand...
Click to collapse
Prior to all this madness, I did try flashing JediMasterX2(I think) and AOKP, two ROMs that I would heavily associate with being stable and basically have everything work. Unfortunately, they didn't work. After all that went down and I restored my backed-up OTA all the way to now, it has been on MK7 stock kernel since then. I'm about to flip a table or something.
Hi xda, I hope your Friday is going well.
EDIT: My calling problem was not fixed. I reflashed 4.4.2 NB4 Modem (twice to make sure it stuck) and the calling still does not work. Did something just completely fry when I had CM11 on this thing? Any ideas anybody? I don't even hear a dial tone if I am the one dialing out, the call still goes through though.
Everything below was my original post which has been resolved, didn't want to start a new thread though.
-----------------------------------------------------------------------------------------
TL;DR: My T-Mobile Samsung Galaxy S 4 (SGH-M919) is unable to boot stock rom, and I am unable to enter recovery. I get seandroid messages trying to do either. Fortunately, the phone can enter download mode. What do I need to do or flash to get this phone booting again? Thank you in advance for taking the time to read and help out.
Below is the long story with details:
1. The phone was given to me running stock Android/TouchWiz. Unfortunately, I do not know what version but I assume it was whatever was the latest version as of late April.
2. I rooted the phone using Odin and CF Auto Root.
3. I created a backup of this newly rooted stock rom.
4. I flashed Cyanogenmod 11
5. After a while I discovered that I could answer calls but I could not hear nor be heard during the call.
6. I restored to the stock rom using the backup I made in step 3.
7. The calling issue continued, so I figured I would just unroot and go back to like-new factory settings. This way I could take the phone in to be repaired or whatever.
8. Following this thread: http://forum.xda-developers.com/showthread.php?t=2336392, I attempted to flash k0nane's UVUAMDL Official Tar
9. Odin got stuck connecting to my device, I believe it was because I did not run Odin as admin. I pulled the battery and repeated this step while running Odin as admin.
10. The flash was successful, however during the phone's first boot it got stuck on the T-Mobile splash screen for about 30 minutes or so. I pulled the battery again.
11. Anytime I put the battery back in the phone, it will attempt to boot and hang at the T-Mobile screen, I believe this is a boot loop?
Looking online, people suggest going into recovery and wiping but I cannot enter recovery. I just get the seandroid not enforcing messages. I'm very hesitant to keep looking through the forums and trying things because I feel like I'm on the edge of bricking the phone if I haven't already.
I don't think the flash was successful because it wouldn't give you those messages, and you would need to flash either 4.3 or 4.4.2 not 4.2.2 (MDL) Try flashing a newer firmware version.. If it was updated to the newest then I would try 4.4.2
Sent from my SGH-M919 using Tapatalk
serio22 said:
I don't think the flash was successful because it wouldn't give you those messages, and you would need to flash either 4.3 or 4.4.2 not 4.2.2 (MDL) Try flashing a newer firmware version.. If it was updated to the newest then I would try 4.4.2
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Ok so I flashed the wrong rom then. I hate to ask but where could I find a 4.4.2 stock rom? I just found a rom I believe will work but the file is titled "M919UVUFNB4_M919TMBFNB4_TMB" not sure if this is 4.4.2 or newer?
You download the stock 4.4.2 ROM from sammobile:
http://www.sammobile.com/firmwares/
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
You download the stock 4.4.2 ROM from sammobile:
[link removed]
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is where I obtained the rom above that I wasn't sure was the newest.
I flashed this rom and everything worked, thank you both.
Any ideas on what happened with the phone call issue? My friend that gave me the phone said it was working just fine when she had it, so I assume somehow the rooting or CM11 screwed something up? Weirdly, calling through WiFi works just fine.
THVRSDAY said:
This is where I obtained the rom above that I wasn't sure was the newest.
I flashed this rom and everything worked, thank you both.
Any ideas on what happened with the phone call issue? My friend that gave me the phone said it was working just fine when she had it, so I assume somehow the rooting or CM11 screwed something up? Weirdly, calling through WiFi works just fine.
Click to expand...
Click to collapse
The only thing that can foul up your phone like that would be a bad cm flash or preflash, it's super important to read and read again, check the thread for support from members and resolutions to problems before you consider the build for your phone. Ask questions and double check everything before you take the plunge.
I assume that the calling problem is fixed, a corrupt modem may cause that and re flashing the modem will correct this.
Pp.
sent from my bluetooth controlled toaster that also takes pictures.
PanchoPlanet said:
The only thing that can foul up your phone like that would be a bad cm flash or preflash, it's super important to read and read again, check the thread for support from members and resolutions to problems before you consider the build for your phone. Ask questions and double check everything before you take the plunge.
I assume that the calling problem is fixed, a corrupt modem may cause that and re flashing the modem will correct this.
Pp.
sent from my bluetooth controlled toaster that also takes pictures.
Click to expand...
Click to collapse
The calling problem was not fixed. I reflashed 4.4.2 NB4 Modem (twice to make sure it stuck) and the calling still does not work. Did something just completely fry when I had CM11 on this thing? Any ideas anybody?
THVRSDAY said:
The calling problem was not fixed. I reflashed 4.4.2 NB4 Modem (twice to make sure it stuck) and the calling still does not work. Did something just completely fry when I had CM11 on this thing? Any ideas anybody?
Click to expand...
Click to collapse
Did you flash the NB4 firmware twice? Firmware, not modem
Sent from my SGH-M919 using Tapatalk
serio22 said:
Did you flash the NB4 firmware twice? Firmware, not modem
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
No, I only flashed the NB4 modem bin found here: http://forum.xda-developers.com/showthread.php?t=2678774. I need to flash the whole NB4 tar twice as well?
THVRSDAY said:
No, I only flashed the NB4 modem bin found here: http://forum.xda-developers.com/showthread.php?t=2678774. I need to flash the whole NB4 tar twice as well?
Click to expand...
Click to collapse
Well modem didn't work so try the firmware
Sent from my SGH-M919 using Tapatalk
serio22 said:
Well modem didn't work so try the firmware
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I flashed the NB4 tar from sammobile twice, calls still not working. I feel like I'm not flashing the correct thing or something.
Using the Android System Info app, every entry has something in it except for Radio. It just says "Radio: unknown". Does this have anything to do with anything?
THVRSDAY said:
I flashed the NB4 tar from sammobile twice, calls still not working. I feel like I'm not flashing the correct thing or something.
Using the Android System Info app, every entry has something in it except for Radio. It just says "Radio: unknown". Does this have anything to do with anything?
Click to expand...
Click to collapse
That is a problem.. How did you get this device?
Sent from my SGH-M919 using Tapatalk
serio22 said:
That is a problem.. How did you get this device?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
My friend gave the phone to me. She got an S5 and didn't want to bother with selling this S4 so she just gave it to me. It was completely pure and stock, with calls working. Something screwed up during the CM11 flash I guess.
WiFi calls still work, everything works except calls.
Maybe I'm doing something wrong? I flashed the sammobile NB4 tar twice via PDA in Odin as usual. For the modem, I flashed the modem bin via Phone in Odin twice. Thank you for your help, by the way.
New term for CM, "complicated maneuver" ,.
Reflashing firmware may do it. Can't hurt either.
Pp.
Sent from my SGH-M919 using XDA Premium 4 mobile app
THVRSDAY said:
My friend gave the phone to me. She got an S5 and didn't want to bother with selling this S4 so she just gave it to me. It was completely pure and stock, with calls working. Something screwed up during the CM11 flash I guess.
WiFi calls still work, everything works except calls.
Maybe I'm doing something wrong? I flashed the sammobile NB4 tar twice via PDA in Odin as usual. For the modem, I flashed the modem bin via Phone in Odin twice. Thank you for your help, by the way.
Click to expand...
Click to collapse
I think something definitely went wrong.. Try flashing this firmware, it flashes better for most people http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip after that, factory reset and if that still doesn't work then you have a bigger problem.. Good luck!
Sent from my SGH-M919 using Tapatalk
serio22 said:
I think something definitely went wrong.. Try flashing this firmware, it flashes better for most people http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip after that, factory reset and if that still doesn't work then you have a bigger problem.. Good luck!
Click to expand...
Click to collapse
I flashed both Fenny's firmware and a baseband he also provided. Did both twice, and calls are still not working.
I was doing some research on this whole "Radio: Unknown" thing and I started seeing threads talking about flashes corrupting the phone's EFS partition. I never made a backup of mine, so I have nothing to restore to. Is it possible that I could use someone else's EFS backup and then use it to restore my phone's EFS partition? Does it work like that?
THVRSDAY said:
I flashed both Fenny's firmware and a baseband he also provided. Did both twice, and calls are still not working.
I was doing some research on this whole "Radio: Unknown" thing and I started seeing threads talking about flashes corrupting the phone's EFS partition. I never made a backup of mine, so I have nothing to restore to. Is it possible that I could use someone else's EFS backup and then use it to restore my phone's EFS partition? Does it work like that?
Click to expand...
Click to collapse
No it will not work, this is device specific afaik.. Like I said earlier, I recommend you call T-Mobile for a replacement
Sent from my SGH-M919 using Tapatalk
Flashing modems and such with a custom rom installed often fails. Did you try doing a restore to full stock using Odin?
It sounds like the phoen has Android 4.4 on it already so you will need to flash the full 4.4 package (can't go back to 4.3 or 4.2)
Try and, boot hte phoen without modifying it, and see if calls work then.
The EFS thing is about the IMEI number. Does your device show an IMEI number in settings? If it does, your EFS isn't the problem. If it doesn't....well then yeah. Problem is pretty much narrowed down.
Skipjacks said:
Flashing modems and such with a custom rom installed often fails. Did you try doing a restore to full stock using Odin?
It sounds like the phoen has Android 4.4 on it already so you will need to flash the full 4.4 package (can't go back to 4.3 or 4.2)
Try and, boot hte phoen without modifying it, and see if calls work then.
The EFS thing is about the IMEI number. Does your device show an IMEI number in settings? If it does, your EFS isn't the problem. If it doesn't....well then yeah. Problem is pretty much narrowed down.
Click to expand...
Click to collapse
I have restored the phone to full stock and have been using it that way since I started this thread. Everything is just like fresh from the factory (except for the knox counter being tripped obviously). Calls still didn't work. An IMEI number still shows up the phone's settings. Using WiFi calling hasn't been that bad at all, but I'm screwed in the case of a real emergency with this thing.