Am I the only one with videotron that is getting the error when trying to flash any of the new MD5 rom. Did a FW and tried all of the new rom's and no matter which one I install I'm getting the error process.android.phone FC. Even went back to stock and nothing is working
Thanks
rener78 said:
Am I the only one with videotron that is getting the error when trying to flash any of the new MD5 rom. Did a FW and tried all of the new rom's and no matter which one I install I'm getting the error process.android.phone FC. Even went back to stock and nothing is working
Thanks
Click to expand...
Click to collapse
Perhaps this T999 4.1.2 firmware update was not meant for your videotron phone.
It looks like you will need to get a hold of the stock Odin flash rom for your phone
and Odin flash it before you can do anything else.
Here is the link for the Odin Flash stock Videotron firmware for your phone in case you want
to flash it and start over again: http://www.androidfilehost.com/?fid=9390225151984927270
Misterjunky said:
Perhaps this T999 4.1.2 firmware update was not meant for your videotron phone.
It looks like you will need to get a hold of the stock Odin flash rom for your phone
and Odin flash it before you can do anything else.
Here is the link for the Odin Flash stock Videotron firmware for your phone in case you want
to flash it and start over again: http://www.androidfilehost.com/?fid=9390225151984927270
Click to expand...
Click to collapse
I did that and I still got the error :s
re: fc
rener78 said:
I did that and I still got the error :s
Click to expand...
Click to collapse
Try this:
Go into CWM or TWRP recovery and "Fix Permissions" then reboot.
If you still have the problem go into CWM or TWRP again and do a
factory reset/wipe cache/wipe dalvik cache but do not wipe system.
After doing that fix permissions again and reboot the phone.
Thanks alot but I give up I've tried what you told me and I still get the error. I guess it's just not ready as you said...Thanks alot again
Misterjunky said:
Try this:
Go into CWM or TWRP recovery and "Fix Permissions" then reboot.
If you still have the problem go into CWM or TWRP again and do a
factory reset/wipe cache/wipe dalvik cache but do not wipe system.
After doing that fix permissions again and reboot the phone.
Click to expand...
Click to collapse
Are you just trying to flash the firmware? If so is there any you can flash so that its back to normal and working? You mentioned the error happened when trying to use the vtron fw is why I ask.
If you can get it working, flash jovys stock rom instead of the firmware. I dont see why this wont work if your up and running beforehand.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Are you just trying to flash the firmware? If so is there any you can flash so that its back to normal and working? You mentioned the error happened when trying to use the vtron fw is why I ask.
If you can get it working, flash jovys stock rom instead of the firmware. I dont see why this wont work if your up and running beforehand.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I tried to flash Jovy's stock MD5 rom and got the FC error, so I decided to go back to rooted stock and then flashing back Jovy's and other MD5 rom and still getting the FC. Will now try Jamieson rom and see from there again. Will post the results.
EDIT Still a no go under Infamous as well. Freaking mad
Thanks
Thats odd. It should work. Let me know how the other goes. Im out until a little later tonight so may not reply for a bit. Good luck!
Sent from my SGH-T999 using xda premium
I'm with Videotron I did get that error, try an original AOSP or CM ROM... Sometimes other ROMS implements T-Mobile features that our SIM i'snt compatible like the Mobile HotSpot App. And dont forget to fully wipe and factory reset it after !
Do you happen to have mobile odin pro? If so, try flashing the root66 firmware that way. Deselect the modem and flash.
Be prepared with a backup and with odin and your stock firmware though, just in case.
The more I think about it, the more I wonder if its a kernel issue. Youre still using your vtron 4.1.1 kernel with tmobiles 4.1.2 system. Before trying the fw, try flashing the kernel that comes with md5. If you cant find it ill post it up in a while.
I dont know how likely this is the prob, but may be worth trying...
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Do you happen to have mobile odin pro? If so, try flashing the root66 firmware that way. Deselect the modem and flash.
Be prepared with a backup and with odin and your stock firmware though, just in case.
The more I think about it, the more I wonder if its a kernel issue. Youre still using your vtron 4.1.1 kernel with tmobiles 4.1.2 system. Before trying the fw, try flashing the kernel that comes with md5. If you cant find it ill post it up in a while.
I dont know how likely this is the prob, but may be worth trying...
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thanks again I have tried with a 4.1.2 kernel and it's still not working, I couldn't find anywhere the kernel coming with MD5. Looked in [Baseband] ALL T999(V) Modems! w/ MAP and Data Tweaks! and couldn't find it aswell.
Cause I used multi-carrier rom 4.1.2 before, Sprint, AT&T, Verizon but for some reason this one is giving a hell of a time.
Even tried an AT&T port of this T-mobile update and it wasn't working
Thanks alot again I really appreciate it
Well there's an update. None of the MD5 rom is working for me I always get the error. But 4.1.2 ports from other carriers are working. Really strange. So I guess I just need to wait for the official update.
**Edit** Well stockorama is actually working.. Weird
Is there anyone with a videotron sgs3 running an MD5 rom?? Cause I can't, only stockorama 2 other than that I cannot..
Related
I bought a T-Mobile Galaxy S 3 LTE with model number SGH-T999L. I used Odin V3 1.85 to flash TWRP recovery and CyanogenMod 10.0.0.
Everything went well but my camera doesn't work. On launching the camera, I get a "Can't connect to camera" error and it quits. The same behavior is observed when using other camera apps. I tried the instructions in this thread(http://forum.xda-developers.com/showthread.php?t=2239414) but it did not fix my problem. I now want to go back to my stock ROM. I successfully downloaded and flashed stock recovery using Odin. However, Odin fails when I try to flash the stock ROM obtained from the samsung website. It gives me a "write failed" error and stops. Any tips or suggestions to help me out would be appreciated. Thanks
Is it supposed to use T999 firmware?
Only odin flash T999L firmware. I dont see it released yet at samsing-updates.com though.
Maybe samfirmware.com? I can look later.
Sent from my SGH-T999 using xda premium
re: sure fix
newidforu said:
I bought a T-Mobile Galaxy S 3 LTE with model number SGH-T999L. I used Odin V3 1.85 to flash TWRP recovery and CyanogenMod 10.0.0.
Everything went well but my camera doesn't work. On launching the camera, I get a "Can't connect to camera" error and it quits. The same behavior is observed when using other camera apps. I tried the instructions in this thread(http://forum.xda-developers.com/showthread.php?t=2239414) but it did not fix my problem. I now want to go back to my stock ROM. I successfully downloaded and flashed stock recovery using Odin. However, Odin fails when I try to flash the stock ROM obtained from the samsung website. It gives me a "write failed" error and stops. Any tips or suggestions to help me out would be appreciated. Thanks
Click to expand...
Click to collapse
Why not reflash the stock ODIN flash rom and make sure it all works ok for you, that will tell you exactly what the problem is.
If the stock rom is working properly, then there is only one thing left which is the culprit and that is the CM10/AOKP/AOSP
or PORTED roms which many people seem to like flashing.
The CM10/AOKP/AOSP and ported roms are excellent if you are a developer or if you like to do a lot of experimentation with your phone.
So the thing to do now is reboot your phone to recovery mode, do a "Factory Reset", "Wipe Cache", "Wipe System" and "Wipe Dalvik".
When that's done Open Odin and put the stock rooted T999 Tmobile Jellybean 4.1.2 into Odin's PDA slot, go into download mode
and once you see Odin is connected to the phone start the flash. Have patience for the phone to boot after its done flashing.
Here is the stock rooted Odin flash T999 Tmobile Jellybean 4.1.2 rom that you can download if you like: T999_UVDMD5
Official JB Firmware - Latest JB 4.1.2 Firmware
My suggestion to you is to only flash Samsung T999 Tmobile stock based Jellybean 4.1.1 or 4.1.2 roms in the future.
But who am I to say whats best..... This is just my personal opinion...... Which usually is not worth a dime. LOL
Sorry, but untill we know more about it, I would not flash T999 firmware onto the T999L.
Its only been out a day and tgey are different model phones with different hardware.
If you decide to try anyway, please post your results
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Sorry, but untill we know more about it, I would not flash T999 firmware onto the T999L.
Its only been out a day and tgey are different model phones with different hardware.
If you decide to try anyway, please post your results
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I am a newbie. I thought the T999 was the same as the T999L. That would explain why Odin doesnt flash stock T999 onto my device. Can anyone here post a link to the stock SGH-T999L ROM?
Just did a quick check and I dont see that the firmware has been made available for download yet.
If you want stock I would flash one of the stock based custom roms via recovery for now.
Out of curiosity, what is your current baseband version?
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Just did a quick check and I dont see that the firmware has been made available for download yet.
If you want stock I would flash one of the stock based custom roms via recovery for now.
Out of curiosity, what is your current baseband version?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Baseband version is T999LUVAMB7. Still waiting for stock ROM to be released on samsung-updates or sammobile.
newidforu said:
Baseband version is T999LUVAMB7. Still waiting for stock ROM to be released on samsung-updates or sammobile.
Click to expand...
Click to collapse
I had the same issue with the same phone. Got it 2 weeks ago haha. Did you happen to make a backup first using CWM Recovery? If so, you can just restore that backup and you'll have your camera functionality back. It's pretty annoying switching back and forth from CM10.1 back to stock just to take pictures but Rom manager makes it pretty quick and effortless.
Actually now that I think of it, they prob wont release the original firmware. Seems like the first build is never available, only when an update is released do we get firmware we csn download.
I am working with another member on getting something going for the T999L, but right now we are stuck until a verified safe method of rooting is found. (Dont want to flash a recovery or cf autoroot w/o knowing it wont screw something up)
Itll happen, but we just gotta be patient.
Just reread the op and see that you say you flashed TWRP. So you were able to initially gain root without any problems?
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Actually now that I think of it, they prob wont release the original firmware. Seems like the first build is never available, only when an update is released do we get firmware we csn download.
I am working with another member on getting something going for the T999L, but right now we are stuck until a verified safe method of rooting is found. (Dont want to flash a recovery or cf autoroot w/o knowing it wont screw something up)
Itll happen, but we just gotta be patient.
Just reread the op and see that you say you flashed TWRP. So you were able to initially gain root without any problems?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I used Odin to flash Clockwork Mod recovery first. I did not like Clockwork Mod's interface and reflashed with TWRP. I had no problems to gain root with either of these methods. I also tried Cyanogenmod stable 10.0.0 and then 10.1 RC2 without any problems. As far as I can tell, all apps work except for the camera. One word of caution though. As you can see from my posts, I am new and dont know what I am doing. I might have just gotten lucky since my device is still unbricked. I had only one "scary" moment during the entire process. I used TWRP to wipe my phone clean and was stuck with no OS install file. ADB sideload did not work since it could not recognize the device at that point. Luckily, I had a micro SD card lying around and was able to put in a new OS install file using my laptop and then TWRP was able to handle it.
tsticge aye
faytx1 said:
I had the same issue with the same phone. Got it 2 weeks ago haha. Did you happen to make a backup first using CWM Recovery? If so, you can just restore that backup and you'll have your camera functionality back. It's pretty annoying switching back and forth from CM10.1 back to stock just to take pictures but Rom manager makes it pretty quick and effortless.
Click to expand...
Click to collapse
Wish I had made a backup! Could you zip up the files contained inside "/system/cameradata/" folder and post a link here? It would help me and anyone else with the same problem restore the camera's functionality. In case you want to try it out, follow the instructions in this link but using the files from your stock backup
http://forum.xda-developers.com/showthread.php?t=2239414
newidforu said:
Wish I had made a backup! Could you zip up the files contained inside "/system/cameradata/" folder and post a link here? It would help me and anyone else with the same problem restore the camera's functionality. In case you want to try it out, follow the instructions in this link but using the files from your stock backup
http://forum.xda-developers.com/showthread.php?t=2239414
Click to expand...
Click to collapse
Here is the cameradata folder from the T999L.
http://d-h.st/Ciy
Good Luck!
How did you get Cyanogenmod installed on the t999l every time i try it aborts with status 7
Mine was failing with this same error. I reverted back to stock, re rooted, then downloaded the flash directly to the phones internal storage. Worked like a champ. I think in my case, there is an issue with the SD card, its kind of old.
Sent from my SGH-T999 using xda app-developers app
Beefstew said:
Mine was failing with this same error. I reverted back to stock, re rooted, then downloaded the flash directly to the phones internal storage. Worked like a champ. I think in my case, there is an issue with the SD card, its kind of old.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
You reverted to stock on the T999L? please exspain how that was done
Re flashed stock ROM using Odin. I believe I got the file from Samsung's website, but I'm not positive of that. I do know its huge, over 1 gig. If you need help with the re flash I know there are already how to's on here about that, so I won't go into it here.
Sent from my SGH-T999 using xda app-developers app
You must be using a T999 as your sig indicates, not a T999L. Am I correct?
Sent from my SGH-T999 using xda premium
Don't I feel like a tool now. Yes Doc, plain old t999 here. Now that I read back through the whole thread here I see that I was being a bit redundant. Now I will return to my closet under the stairs.
Sent from my SGH-T999 using xda app-developers app
No worries! We all do stuff like that from time to time!
Sent from my SGH-T999 using xda premium
I can't flash any TW ROM after flashing cm10.2 I can only flash AOSP ROMs. any advice would help. When I flash TW ROMs it gets stuck on bootloop and yes I do full wipes of everything.
Sent from my SGH-I317 PACMAN 4.3
Jonnyaces187 said:
I can't flash any TW ROM after flashing cm10.2 I can only flash AOSP ROMs. any advice would help. When I flash TW ROMs it gets stuck on bootloop and yes I do full wipes of everything.
Sent from my SGH-I317 PACMAN 4.3
Click to expand...
Click to collapse
Did you flash the downgrade zip in the op of the cm10 thread?
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
Did you flash the downgrade zip in the op of the cm10 thread?
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
No. I didn't know there was one. Thanks for the info. I'm going to check now.
kintwofan said:
Did you flash the downgrade zip in the op of the cm10 thread?
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Do you have a link for that ZIP? I'm running into a similar problem after flashing CM10.2 and can't flash a TW Rom on my S4.
Thanks!
10.2 sucks
the same thing happened to me, but i am using the stock firmware and using a tutorioal on how to unroot unbrick note 2 i hope that brings my phone to normal. and then refalsh and load jedi x 17. ALSO AT ONE POINT I DONT KNOW WHAT I DID WRONG BUT THE PLAY STORE WANTS INCLUDE IN THE 10.2 ROM THAT I INSTALL AND THE WEB PLAY STORE WOULD RECOGNIZE MY DEVICE AS NEXUS 7, BUT IT IS A NOTE 2. THAT WAS WEIRD.
@BB said:
Do you have a link for that ZIP? I'm running into a similar problem after flashing CM10.2 and can't flash a TW Rom on my S4.
Thanks!
Click to expand...
Click to collapse
First page look for restore sd-downgrade.
http://forum.xda-developers.com/showthread.php?t=2105917
downgrade.zip will NOT do ANYTHING to help your issue; all it does it change the files system back to the way it is in 4.12
something else is wrong, but you have to post more info; what rom you flashed, what recovery/version you are on, what the error message/code is when you try to flash, etc...
jon3sh said:
First page look for restore sd-downgrade.
http://forum.xda-developers.com/showthread.php?t=2105917
Click to expand...
Click to collapse
Thanks for the reply ...
wase4711 said:
downgrade.zip will NOT do ANYTHING to help your issue; all it does it change the files system back to the way it is in 4.12
something else is wrong, but you have to post more info; what rom you flashed, what recovery/version you are on, what the error message/code is when you try to flash, etc...
Click to expand...
Click to collapse
Thanks even more for letting me know that this won't do the trick. I should start by reiterating that I have a S4 on Sprint and not a Note 2 on AT&T, so I before I get flamed for being in the wrong forum, just wanted to check if I should go further on what I'm running and the "error" I'm experiencing to see if you can help. I'd really appreciate it if you could but don't want to break any rules ...
its not so much about breaking the rules, as it is about giving you advice that could harm your device, since its not the same as this threads'
I would take it to the s4 threads, just to be sure
good luck
So still no luck with this for me. Someone please help. I can only flash non touchwiz ROMs. I am running pacman nightly 4.3 9-7-13 version. I just flashed devil kernel to see if it would fix the issue. No luck but definetly a nice kernel. I try to flash jedix17 16 and even a nandroid I had from 16 no luck. Tried several other tw ROMs but it just gets stuck on bootloop. Hellllllllllp I like pacman but I was flashing roms everyday and I'm going nuts. I brick my gs3 backup phone so I have to be very careful now with only one phone. Advice?????
Sent from my sgh-i317 using pacman nightly
Okay. ....do you show correct IMEI Number ?
And do you have data ?
If yes. ..then let's try this. ..(deep breath)..(make a backup)...then the following:
First. ...boot to recovery and wipe data, caches, and internal storage. ..
Basically everything without touching your external card. ..and just to be sure. .take it out and set it aside. .(make sure to unmount it in settings first !!!)
Next. .turn off the device and boot into download mode. ..(ready for Odin)
Then using only your PC...download Mr. Robinsons rooted UCAMA4 build from his thread. .. (in the development section)..
Next. ..push the image you just downloaded to the device via Odin. ..(use the PDA box...and don't change any Odin settings)...
Next. ..wait for the image to automatically boot the device once completed. ....(unplug the device)..
If the device fails to boot. ..pull the battery. ..wait 30 seconds. ..then replace it and boot into the newly flashed 3e recovery and wipe cache and data 2 times each. ..then reboot.....
If the device boots normally then move to the next step. ..and if not. ..repeat the flash process again using Odin and the rom you downloaded. ..
If after two unsuccessful flashes, and wipes using 3e recovery, and battery pulls. ..you still don't get a successful boot. ..you may have partition damage. ..in which case a repair may be needed. ..but for the sake of your phone we'll wait until the above has failed. ..
Next. ...If boot occurs using the above method. ..enter your wifi password and log into the play store and download triangle away if you want your counter reset. .
If not. ..skip the play store after entering the wifi password and move into your settings/about phone/software update. ..
Push the update button and wait for ATT to offer you the update to UCAMC3..then take it. ..
If desired you can then clear the flash counter and unroot...
Let's get that far before worrying about anything else. ..
Please record any errors or messages you get. ..especially while using Odin. ..as this tells us the device partition state. ..especially when PIT files are involved. .
Sorry for the long post. ..but it was necessary. ..I hope. .
Please post back. ...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
Guys here is my problem. I tried to upgrade my Samsung N7105 to 4.3 via OTA and it got stucked on bootloop.
I tried to access recovery mode but it fails, only download mode.
What i did is I downloaded the official 4.3 firmware at SamMobile and flashed it with Odin 3.09
Based on Odin it is successful but im still stuck on bootloop and recovery mode cannot still be accessed.
Tried to root it also and installed CWM to recover. I was able to to access CWM
so i restored factory setting, wipe cache and dalvik cache but still the phone bootloops.
Any suggestions on how to resolve my problem?
iamjerbergerber said:
Guys here is my problem. I tried to upgrade my Samsung N7105 to 4.3 via OTA and it got stucked on bootloop.
I tried to access recovery mode but it fails, only download mode.
What i did is I downloaded the official 4.3 firmware at SamMobile and flashed it with Odin 3.09
Based on Odin it is successful but im still stuck on bootloop and recovery mode cannot still be accessed.
Tried to root it also and installed CWM to recover. I was able to to access CWM
so i restored factory setting, wipe cache and dalvik cache but still the phone bootloops.
Any suggestions on how to resolve my problem?
Click to expand...
Click to collapse
just to add, i think i tripped the knox warrant void. its value is now 1 what this means?
Simply flash philz v5.00.5 and it should solve it, here's the link: http://link.tapatalk.com/api/click?...rs.com&subid=c157297d1a1ff043255bfb18530caaa2
Hope it works
With Regards,
Overdub
Sent from my Galaxy Note II using Tapatalk
OverDub said:
Simply flash philz v5.00.5 and it should solve it, here's the link: http://link.tapatalk.com/api/click?...rs.com&subid=c157297d1a1ff043255bfb18530caaa2
Hope it works
With Regards,
Overdub
Sent from my Galaxy Note II using Tapatalk
Click to expand...
Click to collapse
Was able to access custom recovery upon flashing. conducted wipe data / factory reset and wipe dalvik cache but still bootlooping was experienced. Is my phone dead already and needs replacement?
After flashing the philz, try flashing a custom ROM and see if u will unstuck from the bootloop, try cm 10.2, it's very light and mostly bug free
Sent from my GT-N7100 using xda app-developers app
OverDub said:
After flashing the philz, try flashing a custom ROM and see if u will unstuck from the bootloop, try cm 10.2, it's very light and mostly bug free
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Now working cm10.2 but now my next problem is there is no signal. it appeared that imei value is null. how do i repair this? thanks!
By the way after successfully running on cm10.2 I tried to reflash again with stock firmware. bootloop again. i think i will be stuckon using custom roms for now. The only thing I need to address is the no mobile signal problem.
OK so the bootloop problem is done and don't worry there are a lot of amazing custom roms that are based on the stock one and even better features like the note 3 features, as for the imei, please tell me you did an nfs backup if you do, there are a lot of ways you can restore your nfs backup, if you don't have an nfs backup, I don't know what to do.
With Regards,
Overdub
Sent from my GT-N7100 using xda app-developers app
Not very clued up on losing baseband but it happened to me once when I used a different revovery version to restore a back up. Dr Ketan has written a guide on restoring baseband, he will be able to fix it
Sent from my GT-N7105 using XDA Premium 4 mobile app
Please keep us updated and if it is fixed hopefully, please show us what you did.
With Regards,
Overdub
Sent from my GT-N7100 using xda app-developers app
Still not working
OverDub said:
Please keep us updated and if it is fixed hopefully, please show us what you did.
With Regards,
Overdub
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Sorry was on vacation for a long time. I wasn't able to update this thread.
Problem right now is I forgot to back the EFS so when I flashed CM 10.2
There is no baseband and IMEI is null. Tried to flash n7105 modem but still it still doesn't work
Have read that I should flash stock firmware to fix baseband and IMEI but 4.3 firmwares makes my phone go on bootloop.
Should I wait for 4.4 update? I want my phone to make it usable again.
My phone right now is useless and works like an itouch hahaha
Any suggestions???
Need expert advise
iamjerbergerber said:
Sorry was on vacation for a long time. I wasn't able to update this thread.
Problem right now is I forgot to back the EFS so when I flashed CM 10.2
There is no baseband and IMEI is null. Tried to flash n7105 modem but still it still doesn't work
Have read that I should flash stock firmware to fix baseband and IMEI but 4.3 firmwares makes my phone go on bootloop.
Should I wait for 4.4 update? I want my phone to make it usable again.
My phone right now is useless and works like an itouch hahaha
Any suggestions???
Need expert advise
Click to expand...
Click to collapse
You may try Hurricane modem changer and experiment with various modem versions. It's a longshot but it may help. Try finding very old modem version and flash that.
Hurricane Modem Changer is that an application?
Where to get it? Also, will it there be a possibility that when I flash Official 4.4 kitkat (when released) on my n7105.
Bandwidth and IMEI will be restored? I'm leaning towards to come back to touch wiz though many of you guys might say that a custom rom might be better.
For one thing, the problem in my n7105 started when i upgraded to 4.3 via OTA
iamjerbergerber said:
Hurricane Modem Changer is that an application?
Where to get it? Also, will it there be a possibility that when I flash Official 4.4 kitkat (when released) on my n7105.
Bandwidth and IMEI will be restored? I'm leaning towards to come back to touch wiz though many of you guys might say that a custom rom might be better.
For one thing, the problem in my n7105 started when i upgraded to 4.3 via OTA
Click to expand...
Click to collapse
Look HERE. One of the downloads is Hurricane Modem Changer.
mat9v said:
Look HERE. One of the downloads is Hurricane Modem Changer.
Click to expand...
Click to collapse
Thanks will try. Aside from this. Where can I find old modem?
Will hurricane modem changer work if I used ditto note 3 rom?
iamjerbergerber said:
Thanks will try. Aside from this. Where can I find old modem?
Will hurricane modem changer work if I used ditto note 3 rom?
Click to expand...
Click to collapse
Hurricane contains some older modems along with new ones and yes it will work if you used DN3.
mat9v said:
Hurricane contains some older modems along with new ones and yes it will work if you used DN3.
Click to expand...
Click to collapse
Is the hurricane modem changer link you provided will work on n7105? tried to flash it but aroma installer tells its for n7100 international version
iamjerbergerber said:
Is the hurricane modem changer link you provided will work on n7105? tried to flash it but aroma installer tells its for n7100 international version
Click to expand...
Click to collapse
No, it's for N7100 only - the modems are completely different (3G vs LTE).
Please read the original post carefully before flashing, if the HC was not protected you could have lost network functions completely.
mat9v said:
No, it's for N7100 only - the modems are completely different (3G vs LTE).
Please read the original post carefully before flashing, if the HC was not protected you could have lost network functions completely.
Click to expand...
Click to collapse
Im using an n7105 model. Guess this will not work. Any other suggestions?
From what I understand, the quickest solution is to flash stock firmwares however, i'm quite disappointed that
almost all 4.3 firmwares from sam mobile doesn't work in my phone (always bootlooping)
A technician told me that I should wait for the 4.4 kitkat release, since it might work for my phone.
Now my problem is, I need to have the phone operational. so im willing to flash custom roms for the meantime
but the baseband problem is really testing my patience. hehe
iamjerbergerber said:
Im using an n7105 model. Guess this will not work. Any other suggestions?
From what I understand, the quickest solution is to flash stock firmwares however, i'm quite disappointed that
almost all 4.3 firmwares from sam mobile doesn't work in my phone (always bootlooping)
A technician told me that I should wait for the 4.4 kitkat release, since it might work for my phone.
Now my problem is, I need to have the phone operational. so im willing to flash custom roms for the meantime
but the baseband problem is really testing my patience. hehe
Click to expand...
Click to collapse
It's pretty strange really as stock firmwares are a complete set of bootloader/modem/system that should in theory work perfectly well together without any incompatibility problems. Have you ever tried to install one of them without sdcard and/or simcard installed, maybe you have some leftovers from previous system (Android secure directory) that causes bootloops, also did you completely clean internal sdcard prior to flashing, it may create the same problems as external sdcard.
mat9v said:
It's pretty strange really as stock firmwares are a complete set of bootloader/modem/system that should in theory work perfectly well together without any incompatibility problems. Have you ever tried to install one of them without sdcard and/or simcard installed, maybe you have some leftovers from previous system (Android secure directory) that causes bootloops, also did you completely clean internal sdcard prior to flashing, it may create the same problems as external sdcard.
Click to expand...
Click to collapse
im not sure if i cleaned the internal sdcard prior to flashing.
It started with the OTA update that failed then I tried to flash stock firmware via odin
do i have to do a pre-requisite before flashing it again? so you are suggesting to remove the simcard and external sd card prior to flashing?
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.
Using Odin 3.07...Have the tar file in Bootloader slot...Hit start after it recognizes it...Tried different USB Cables...Same thing...Installed Grizzs Recovery without a hitch...But not the Bootloader...Am i using right Odin ??? Want to flash Civatos Kit Kat Rom...Can i flash the zip file for the Bootloader and Modem thru Recovery...Or do I have to go thru Odin...If I have to go thru Odin is there sumthing im doing wrong...Can Sumone enlighten me...
Thanx...
I would suggest that you read the ENTIRE OP of @civato, it states there clearly that the BL needs to be flashed with Odin which is included in the download package, just head on over there and download everything from him,
http://forum.xda-developers.com/showthread.php?t=2759863
Hope this helps
Sent from my SPH-L900 using XDA Premium 4 mobile app
Harjan112 said:
I would suggest that you read the ENTIRE OP of @civato, it states there clearly that the BL needs to be flashed with Odin which is included in the download package, just head on over there and download everything from him,
http://forum.xda-developers.com/showthread.php?t=2759863
Hope this helps
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ok ...I have the tar files for the BL and Modem...I have Odin 3.07...ive tried to flash the BL tar file in Odin...It fails and wont let me do it...Are u tellin me that Odin is in the Aroma Installer and it will let me do it thru that...Or are me and u not on the same page...Ive never had a bad flash of a tar file thru Odin...Thats why im wunderin whats goin on or am i doin sumthin wrong...
Why not try the Full stock kk tar file using Odin? Make sure you put your tablet in download mode.
Sent from my SGH-I317 using Tapatalk
pvsgh said:
Why not try the Full stock kk tar file using Odin? Make sure you put your tablet in download mode.
Sent from my SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Finally Flashed Bootloader thru Odin 3.09 was usin 3.07 wudnt flash...Flashed Civatos Custom Rom...Now stuck in Fen Bootloop...Got to see whats next,,,Sumone said kernel...Got to flash right one...Thinkin stock i dont know...I dont like stock anything...thats why i flash...
ronny71 said:
Finally Flashed Bootloader thru Odin 3.09 was usin 3.07 wudnt flash...Flashed Civatos Custom Rom...Now stuck in Fen Bootloop...Got to see whats next,,,Sumone said kernel...Got to flash right one...Thinkin stock i dont know...I dont like stock anything...thats why i flash...
Click to expand...
Click to collapse
Alright first things first.... what model do you have???
The kernel is included with civato's Rom so you should not have problems with that.
I don't believe you can flash another kernel yet until dev's have a source that they can work with and create different kernel, so I would NOT flash a JB kernel on a KK Rom.
Did you do a full wipe before you flashed civato's Rom "as stated in the OP"?
What you could try is a factory reset in your recovery or a wipe cache and reboot again this might get you out of the boot loop.
Hoping this helps.
Sent from my SPH-L900 using XDA Premium 4 mobile app
ronny71 said:
Finally Flashed Bootloader thru Odin 3.09 was usin 3.07 wudnt flash...Flashed Civatos Custom Rom...Now stuck in Fen Bootloop...Got to see whats next,,,Sumone said kernel...Got to flash right one...Thinkin stock i dont know...I dont like stock anything...thats why i flash...
Click to expand...
Click to collapse
in aroma choose the stock kernel option. I had the same bootloop problem ....it kept going into recovery.
After choosing the stock kernel everything was smooth.
Harjan112 said:
Alright first things first.... what model do you have???
The kernel is included with civato's Rom so you should not have problems with that.
I don't believe you can flash another kernel yet until dev's have a source that they can work with and create different kernel, so I would NOT flash a JB kernel on a KK Rom.
Did you do a full wipe before you flashed civato's Rom "as stated in the OP"?
What you could try is a factory reset in your recovery or a wipe cache and reboot again this might get you out of the boot loop.
Hoping this helps.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wiped cash again...Did Factory Reset...Still returns me to Recovery...
Model is 5110...
Thre isnt a choice to install Stock Kernel in Aroma ...
ronny71 said:
Wiped cash again...Did Factory Reset...Still returns me to Recovery...
Model is 5110...
Click to expand...
Click to collapse
As @pvsgh suggested too try installing stock KK Rom first and then follow everything to the letter from civato's OP and I really do mean step by step and you should not have any problems.
Hoping this helps.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Harjan112 said:
As @pvsgh suggested too try installing stock KK Rom first and then follow everything to the letter from civato's OP and I really do mean step by step and you should not have any problems.
Hoping this helps.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah im goin to Odin back to stock KK...Then redo Civatos Rom...
I followed step by step, I'm familiar with the process, I posted my own thread, not realizing that he was having the issue with civato's Rom as well, because I had no issues with the bootloader, I'm running kitkat stock right now, but following everything weird for word, even going so far as multiple wipes, directly after Odin flash of stock kitkat, put me in the same predicament as the OP. Also worth noting, restoring a nandroid of stock kit Kat after attempting to flash the Rom fixes nothing. The boot loop persists, though data remained after Odin flashing stock again, just had to re root.