Database Develop

WTF is going on with Sprint Visual Voicemail

Voicemail not working after flashing to new ROM, tried 3 roms none of them r giving me voicemail. LIQUIDSENSE 2.1, ALOYSIOUS 2.1, NFX hero 2.2, whats the problem. I get a message in tool bar that cant be cleared "A mandatory update is available", but when i try to upgrade i get "General failure. Please try again at a later time"
What to do any suggestions. Ive been hearing bout using google voice, but im kinda lost on that.
PLZ SOMEBODY HELP

cperkins0 said:
Voicemail not working after flashing to new ROM, tried 3 roms none of them r giving me voicemail. LIQUIDSENSE 2.1, ALOYSIOUS 2.1, NFX hero 2.2, whats the problem. I get a message in tool bar that cant be cleared "A mandatory update is available", but when i try to upgrade i get "General failure. Please try again at a later time"
What to do any suggestions. Ive been hearing bout using google voice, but im kinda lost on that.
PLZ SOMEBODY HELP
Click to expand...
Click to collapse
go back to stock 2.1 update the app from there, then backup the .apk (astro file explorer has a tool that allows you to do this) then install it in the other builds

which file is it in? I can't find it

its called com.core.apk or something like that im not sure where it hangs out

cmyasika1 said:
which file is it in? I can't find it
Click to expand...
Click to collapse
thoughtlesskyle said:
its called com.core.apk or something like that im not sure where it hangs out
Click to expand...
Click to collapse
Yeah, it's something like that in system/app

sprint_core.apk in /system/app there may be an odex. i always rm NameOfApp.*
if you delete the apk it may cause problems(maybe. didnt for me but has for others). you also wont be notified of vm's. youll have to call to check. on a 2.1 rom, that is. thats how it worked for me anyway.
personally, my vm isnt working on my new device. like it never set itself up correctly. if anyone should happen to have a link to some instructions to set this up, that would be fantastic. I hate calling the silly people at sprint. thank you

bump this. need help.

vrundmc said:
bump this. need help.
Click to expand...
Click to collapse
Did you try flashing the version in my sig?

theimpaler747 said:
Did you try flashing the version in my sig?
Click to expand...
Click to collapse
i havent tried that as im having annoying problems with my vvm on my device.
http://forum.xda-developers.com/showthread.php?t=855545
guess ill try to use this one here.

tailsthecat3 said:
i havent tried that as im having annoying problems with my vvm on my device.
http://forum.xda-developers.com/showthread.php?t=855545
guess ill try to use this one here.
Click to expand...
Click to collapse
Try flashing my version, let me know how it goes!

theimpaler747 said:
Did you try flashing the version in my sig?
Click to expand...
Click to collapse
Flashed your file...same issue...delay in setting up voicemail... Flashed and restarted. Even tried rebooting. No go. My activation message is stuck in the undelivered box.

theimpaler747 said:
Try flashing my version, let me know how it goes!
Click to expand...
Click to collapse
it didnt work. i removed the original, flashed yours. still have the undelivered message, the activation message. nothing is working, i cant figure it out. and when i called sprint, they reset my vm, so i lost messages and had to set up everything again...

FYI to Impaler, your VVM version in your sig works for those in areas where an official update has not rolled through yet.
Don't know if you are aware, but Sprint recently updated the VVM software to version T.5.1.0.48 (here in TX it was updated the last week of October). Note that Sprint CSR will not be able to help you reset it unless you are on a Sense ROM. Period.
Two options to fix on your non-Sense ROM... there is an updated .apk floating around on these boards (might need to PM someone for it). Get it and install via your file manager.
Or...
Other way is to nandroid your current ROM, then flash a Sense ROM like Fresh's most current. Then, update your PRL and Profile, then go into the VVM and press Menu and update Sprint VVM.
Then, either try to nandroid back to your original ROM and check to see if that does it (haven't tried that, but it might work)... or else... yes, you will need to pull the updated com.coremobility.app.vnotes from the Sense ROM and install the pulled .apk into your new ROM.
Hope this helps.

mr. implaler, I have used yours for the last weeks successfully, so thank you. I just ran into the same problem with the mandatory upgrade, and it is an update i did before I rooted my phone. the VM did work this morning on MUIU but i loaded MYN and that is when my issue started.
Hope someone can firgure it out
thanks again implaler

mine just actually updated and works and phone didn't unroot

vrundmc said:
Flashed your file...same issue...delay in setting up voicemail... Flashed and restarted. Even tried rebooting. No go. My activation message is stuck in the undelivered box.
Click to expand...
Click to collapse
Here is my solution.
http://forum.xda-developers.com/showthread.php?t=855545
I had 9016 in the blocked texts list. Hope this helps you.

Excellent...let me add to this...
I suppose using variations of ROMS that don't include VVM and block 9016 caused this issue.
You can unblock 9016 by going to your account online, under "My Devices," then "My Preferences." Scroll down to the "Limits and permissions" section. You will see the "Block Texts" link there.

vrundmc said:
Flashed your file...same issue...delay in setting up voicemail... Flashed and restarted. Even tried rebooting. No go. My activation message is stuck in the undelivered box.
Click to expand...
Click to collapse
tailsthecat3 said:
it didnt work. i removed the original, flashed yours. still have the undelivered message, the activation message. nothing is working, i cant figure it out. and when i called sprint, they reset my vm, so i lost messages and had to set up everything again...
Click to expand...
Click to collapse
Hmm... I still can't tell if this is a Sprint or a root issue....

alaman68 said:
mr. implaler, I have used yours for the last weeks successfully, so thank you. I just ran into the same problem with the mandatory upgrade, and it is an update i did before I rooted my phone. the VM did work this morning on MUIU but i loaded MYN and that is when my issue started.
Hope someone can firgure it out
thanks again implaler
Click to expand...
Click to collapse
No problem, glad it worked well for you

jedijackie said:
FYI to Impaler, your VVM version in your sig works for those in areas where an official update has not rolled through yet.
Don't know if you are aware, but Sprint recently updated the VVM software to version T.5.1.0.48 (here in TX it was updated the last week of October). Note that Sprint CSR will not be able to help you reset it unless you are on a Sense ROM. Period.
Two options to fix on your non-Sense ROM... there is an updated .apk floating around on these boards (might need to PM someone for it). Get it and install via your file manager.
Or...
Other way is to nandroid your current ROM, then flash a Sense ROM like Fresh's most current. Then, update your PRL and Profile, then go into the VVM and press Menu and update Sprint VVM.
Then, either try to nandroid back to your original ROM and check to see if that does it (haven't tried that, but it might work)... or else... yes, you will need to pull the updated com.coremobility.app.vnotes from the Sense ROM and install the pulled .apk into your new ROM.
Hope this helps.
Click to expand...
Click to collapse
Ok cool, well glad it worked for a few people

Someone please help newb with brick

I have been looking through the threads, and havent seen what I am looking for. So hopefully i will not get flamed to bad. I tried to install mikeymikes GR12, I got through the first stage of downloading the gingerbread rom to the phone through odin, but then it went south. I lost root and was unable to get back to the download screen. I then tried to use the all in one tool to root the phone, and that put me to the recovery screen where i could not use the ok button, just the volume up and down buttons. I just managed to get the download screen to come back, but i cant get anything else to work. Any suggestions on what to do, where to go from here.
Thank you for your help

I would go back to stock first. I believe your problem lies in the bootloaders. There are two bootloaders in the beginning and if you don't have the gingerbread ones installed, you won't install gingerbread properly.
I would use DesignGears One Click Odin to go back to stock and load the Froyo drivers. http://forum.xda-developers.com/showthread.php?t=731989. Make sure you open up Odin first before plugging in your phone, then hit the Start button.
Once that is done, you can try again, but read about getting the GB bootloaders installed properly before you try to flash a GB ROM. Any of the GB ROM instructions should get you there. Just make sure you know all the steps before you try it again.
Good Luck!!

I don't see why you would be flamed for your question. That is what Q&A is for and you are in a bad spot. The biggest thing to remember is to be as specific as possible when you post a question. This includes what you were trying to do, what steps you took, what was the result, when did the problem occur (which step) and what you have tried to do, if anything to fix it.

One more thing. It is always possible that the USB cable is bad or that the USB port you are plugging into (on the computer) isn't working properly. You might also want to plug into a different USB port.
Sorry these posts are broken up, but as I'm coming up with ideas, I'm posting.

Here's something you should try:
(I wrote this for Team Phoenix, hence the sig.. But it works the same with every ROM. There's a link to a very nice tutorial I suggest you follow).
http://forum.xda-developers.com/showpost.php?p=13503747&postcount=2
Hope it helps

You guys are awesome, Odin one click worked, It's on eclair, but it works! Thank you again

donkeyboy said:
You guys are awesome, Odin one click worked, It's on eclair, but it works! Thank you again
Click to expand...
Click to collapse
Glad it worked!
Make sure you read and understand before going forward with flashing
Otherwise... well.. I'll still be in here ready to help lol

BWolf56 said:
Glad it worked!
Make sure you read and understand before going forward with flashing
Otherwise... well.. I'll still be in here ready to help lol
Click to expand...
Click to collapse
Me too. If we can ... Remember not all things can be recovered from so please read everything twice before ever touching your phone.

10-4. My next question is: where do I get froyo from. Kies sees my eclair version as unregistered, so it wont update. And my ota sees an update is needed, but when i tried, the area im in has crappy signal, so the update failed and now i have to wait 24 hours to do it.
Any suggestions?
Thanks again

are you planning on flashing a custom rom?
if so updating to official froyo is A HUGE WASTE OF TIME
EDIT:are you Canadian by chance? if so check this thread:http://forum.xda-developers.com/showthread.php?t=979133

I only plan to root the official froyo right now, that is what I had before I jacked it up. I am not Canadian.

donkeyboy said:
I only plan to root the official froyo right now, that is what I had before I jacked it up. I am not Canadian.
Click to expand...
Click to collapse
Going on official froyo will get you the signature failed error (which you need the 3e recovery fix if you ever want to flash a custom ROM).
So, basically, if you want more than 2.2 official release. We suggest you don't update. If you're perfectly fine staying on 2.2 Froyo, then there's no problem lol
As for Kies, you shouldn't have any problem using Kies mini. Other than that, there is a 2.2 flash around here. I'm sure you'll find it doing a little search

I had root on my official froyo for a couple of months without a problem. Right now i cant get my phone to go into download mode, it only goes to the battery screen. If i can get to download i can make some headway

donkeyboy said:
I had root on my official froyo for a couple of months without a problem. Right now i cant get my phone to go into download mode, it only goes to the battery screen. If i can get to download i can make some headway
Click to expand...
Click to collapse
If the battery pull way isn't working. You could always go read on abd. It send SU commands and you could get your phone in downlaod mode that way.

Is there an easy way to get adb without getting the sdk. I downloaded the sdk and it keeps saying i need java, when i download the java crap it says the same thing.

donkeyboy said:
Is there an easy way to get adb without getting the sdk. I downloaded the sdk and it keeps saying i need java, when i download the java crap it says the same thing.
Click to expand...
Click to collapse
Did you reboot your pc?

Yes i did, no change

i believe you need microsoft .net framework installed also...

easy adb setup link in my sig.
files and everything needed to get going.

you may want to build a jig yourself or buy one online just in case:
MOD EDIT: No links to commercial products please.

[Q] Cannot update to Gingerbread

Hey everyone. I rooted my phone a while back (around June), but it got unrooted during the update in July and I haven't bothered rooting it again. But now, when I try to update to Gingerbread, I always get a message saying "Update failed or incomplete" after downloading and rebooting. I noticed I still have SuperUser installed, so I tried unrooting with SuperOneClick, but SuperOneClick is stuck on "Waiting for Device". I have also tried to reset to factory settings, with the same result. Does anyone know how to fix this? Thanks.

rawrzar said:
Hey everyone. I rooted my phone a while back (around June), but it got unrooted during the update in July and I haven't bothered rooting it again. But now, when I try to update to Gingerbread, I always get a message saying "Update failed or incomplete" after downloading and rebooting. I noticed I still have SuperUser installed, so I tried unrooting with SuperOneClick, but SuperOneClick is stuck on "Waiting for Device". I have also tried to reset to factory settings, with the same result. Does anyone know how to fix this? Thanks.
Click to expand...
Click to collapse
You may not have updated like you thought. V6 should have gotten rid of root for you. I had to do a factory restore, wipe the data and image, all of it. When I went back to do all that stuff, I still had the Bionic splash screen, and it is because of that little change, that I was not able to update myself. You may have something similar going on with your phone, just in a different place. Anything beyond doing that, just ask, but it should take care of you. Make a backup first, just in case. You will have to set everything up again.

markapowell said:
You may not have updated like you thought. V6 should have gotten rid of root for you. I had to do a factory restore, wipe the data and image, all of it. When I went back to do all that stuff, I still had the Bionic splash screen, and it is because of that little change, that I was not able to update myself. You may have something similar going on with your phone, just in a different place. Anything beyond doing that, just ask, but it should take care of you. Make a backup first, just in case. You will have to set everything up again.
Click to expand...
Click to collapse
Thanks for your reply. I have performed a factory reset, but the update still fails. I also notice that after the reset, SuperUser is still listed under my installed apps.

rawrzar said:
Thanks for your reply. I have performed a factory reset, but the update still fails. I also notice that after the reset, SuperUser is still listed under my installed apps.
Click to expand...
Click to collapse
Does the update fail, or does it just say no update available?
Sent from my VS910 4G using xda premium

mtmichaelson said:
Does the update fail, or does it just say no update available?
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
It fails. the update downloads, and reboots to install. But about half way through the installation, the phone reboots again. when the home screen comes up, a screen pops up saying "update failed or incomplete".

I had the same problem. Did you reinstall the stock recovery program? I also had the bionic boot image from revolt1.5, which was messing things up. Once I reverted back to the stock boot image, the update went through.

JohnnyAn said:
I had the same problem. Did you reinstall the stock recovery program? I also had the bionic boot image from revolt1.5, which was messing things up. Once I reverted back to the stock boot image, the update went through.
Click to expand...
Click to collapse
How would I go about reverting back to stock image? sorry , I don't know much about this.

rawrzar said:
How would I go about reverting back to stock image? sorry , I don't know much about this.
Click to expand...
Click to collapse
The cubed had a stock revo file that he posted somewhere in the dev forum. Just flash that with CWM and you should be good to go.
Sent from my VS910 4G using XDA App

I am in a similar situation but when I try to update to gingerbread it says there is no update available. I too still have supreuser installed after reflashing from revolt 1.5 to thcubed zv4 rooted stock and then updating its to zv6. How can I get my phone to download zv7?
Sent from my VS910 4G using XDA App

jdleider said:
I am in a similar situation but when I try to update to gingerbread it says there is no update available. I too still have supreuser installed after reflashing from revolt 1.5 to thcubed zv4 rooted stock and then updating its to zv6. How can I get my phone to download zv7?
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
Apparently the update hasn't been pushed to all phones yet...there's several of us on xda that still don't have it. Jackpot08 is working on a .tot but until then, we just have to wait.
Some people have called Verizon and they can't force the update to your phone, so don't bother with that.

JohnnyAn said:
The cubed had a stock revo file that he posted somewhere in the dev forum. Just flash that with CWM and you should be good to go.
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
Thanks! Found it and got it working. Just waiting for the update now.
jamRwoo said:
Apparently the update hasn't been pushed to all phones yet...there's several of us on xda that still don't have it. Jackpot08 is working on a .tot but until then, we just have to wait.
Some people have called Verizon and they can't force the update to your phone, so don't bother with that.
Click to expand...
Click to collapse
Thanks for the info, guess the update hasn't been pushed to my phone yet.

I have been on stock for a week now, and its been horrible. I forgot how slow this was before devs streamlined the system, and how many rooted apps/functions I used.
I am going back to revolt today. I will see GB when the .TOT is available.

rawrzar said:
Hey everyone. I rooted my phone a while back (around June), but it got unrooted during the update in July and I haven't bothered rooting it again. But now, when I try to update to Gingerbread, I always get a message saying "Update failed or incomplete" after downloading and rebooting. I noticed I still have SuperUser installed, so I tried unrooting with SuperOneClick, but SuperOneClick is stuck on "Waiting for Device". I have also tried to reset to factory settings, with the same result. Does anyone know how to fix this? Thanks.
Click to expand...
Click to collapse
Were you attempting to update to gingerbread by using the TOT? Or was there an update available though your service provider?
If you were getting a failure through the network, it's likely because you haven't gone back to stock recovery and still have ClockWorkMod Recovery installed. Use DevToolKit to fix this.
If you are using the TOT and getting a failure, do a checksum on the TOT file.

I've been working on this actively as I have a revolution. LG has informed me the update push completed on November 2. Nobody at VZW or LG can tell me why some Revolutions haven't gotten the push.
VZW Engineering has apparently been alerted, but LG has been unresponsive to me to-date.
I'm not waiting and putting together a one-package manual update kit, but I do want to give LG and VZW time to give me an update. Thing is, it's been over 72 hours now and there hasn't been one, so my patience is wearing thin.
It's disappointing that LG hasn't responded to any of my inquiries... I'm asking the right people behind the scenes.

hatoncat said:
I've been working on this actively as I have a revolution. LG has informed me the update push completed on November 2. Nobody at VZW or LG can tell me why some Revolutions haven't gotten the push.
VZW Engineering has apparently been alerted, but LG has been unresponsive to me to-date.
I'm not waiting and putting together a one-package manual update kit, but I do want to give LG and VZW time to give me an update. Thing is, it's been over 72 hours now and there hasn't been one, so my patience is wearing thin.
It's disappointing that LG hasn't responded to any of my inquiries... I'm asking the right people behind the scenes.
Click to expand...
Click to collapse
I'm in Rochester NY and never got one. I gave it til 2 days ago and threw on the TOT.

Madert said:
I'm in Rochester NY and never got one. I gave it til 2 days ago and threw on the TOT.
Click to expand...
Click to collapse
Yeah, I'm leaning towards drafting an idiot-proof TOT guide, it's just going to be really upsetting if I have to do that. If this was Apple, and not LG, we wouldn't even have this thread right now.
Option-click .ipk and done... not that Apple would even let ~1-5% of a device "miss" an update.

So, I've confirmed a few things with LG officially:
1) The ZV7 update has not been pulled.
2) LG was not aware of this issue until I reported it.
3) LG is just now starting the process of investigating.
I can't flash a TOT on mine right now, as LG may want to capture my unit for evaluation. I'll know more soon, hopefully by Monday.

Verizon was trying to push an update on me back on the 11th. It was the V6 update, as I was running V4. It failed, and I manually ran the tot through with LGNPST. Since thecubed had posted the V7 tot as well, I ran that through as well.
I probably did not need to go from V4 to V6 to get to V7, but I figured it wouldn't hurt.
But as I said, the only push I had received was on the 11th, well after the 2nd.
As a semi-newbie, it was easier to push the tot on than anything else.

LG Engineering is at least listening... they have agreed to capture my unit and send me a brand new Revolution simultaneously.

antiwesley said:
Verizon was trying to push an update on me back on the 11th. It was the V6 update, as I was running V4. It failed, and I manually ran the tot through with LGNPST. Since thecubed had posted the V7 tot as well, I ran that through as well.
I probably did not need to go from V4 to V6 to get to V7, but I figured it wouldn't hurt.
But as I said, the only push I had received was on the 11th, well after the 2nd.
As a semi-newbie, it was easier to push the tot on than anything else.
Click to expand...
Click to collapse
Did you have clockwork recovery installed when you tried to get Verizon s update
Sent from my gingervolt`ed revolution

[Q]Any details on at&t OTA update?

Subject says it all. No luck with Google. Don't want to update until I know what's being updated.
Sent from my HTC first using xda app-developers app

not sure but...
jonslice said:
Subject says it all. No luck with Google. Don't want to update until I know what's being updated.
Sent from my HTC first using xda app-developers app
Click to expand...
Click to collapse
I installed the update last night. I honestly don't know what all the changes are, but I'm pretty sure it is a bugfix release. Still android 4.1.2. The only thing that I have noticed is that after the update my led will actually flash green for a text message or email. Before the update, my led only worked for charging, so I would have no idea whether I had email or messages without turning my screen on.
I have not noticed any other changes. No noticable speedups or slowdowns. Haven't discovered any issues. None of my apps have ever forced closed on this phone, and that has not changed after the update.
So...not a bad upgrade, although it might be pointless if you don't have any issues.

19.8MB update. Can't be too much going on in there, but I'd also think it's more than a few lines of code being updated...
Ooh, fun. Looks like I can't install the OTA with CWM or TWRP. Jonslice, are you rooted?
EDIT:
Weird. Now my phone says the software is up to date. What's the Build info under About Phone for you guys? Wondering if it did actually update even though it said it failed...

The OTA zip is on my dropbox in case anyone is curious to look at it. [1] Looks to me like it's updating a handful of system files, as well as the boot and recovery images. With clockworkmod installed, I was prompted to confirm installing the update because its signature wasn't verified, but I haven't yet attempted to let it install it. This should definitely give us an "official" image for the boot and recovery partitions though, which never hurts.
1: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/OTAPkg.zip

nuclear_eclipse said:
The OTA zip is on my dropbox in case anyone is curious to look at it. [1] Looks to me like it's updating a handful of system files, as well as the boot and recovery images. With clockworkmod installed, I was prompted to confirm installing the update because its signature wasn't verified, but I haven't yet attempted to let it install it. This should definitely give us an "official" image for the boot and recovery partitions though, which never hurts.
1: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/OTAPkg.zip
Click to expand...
Click to collapse
It'll fail if you try to install it. I'm thinking it needs the official bootloader to work. Someone will need to make this flashable. I was trying to extract it from my phone, but you beat me to it. Thanks!

chrisliphart said:
It'll fail if you try to install it. I'm thinking it needs the official bootloader to work. Someone will need to make this flashable. I was trying to extract it from my phone, but you beat me to it. Thanks!
Click to expand...
Click to collapse
I pulled this recovery.img from the firmware.zip that's included inside OTAPkg.zip: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.img
I would assume that a simple `fastboot flash recovery recovery.img` should suffice.

nuclear_eclipse said:
I pulled this recovery.img from the firmware.zip that's included inside OTAPkg.zip: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.img
I would assume that a simple `fastboot flash recovery recovery.img` should suffice.
Click to expand...
Click to collapse
Huh. I couldn't get the Firmware.zip to open on my system. Thanks for doing that. Now I'm gonna go be an idiot and possibly brick my device by pushing this recovery to my phone to try and install the OTA. lol

I did also manage to snag the recovery.log from clockwork recovery when the update first tried to run, just in case that actually proves useful to anyone... https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.log

nuclear_eclipse said:
I did also manage to snag the recovery.log from clockwork recovery when the update first tried to run, just in case that actually proves useful to anyone... https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.log
Click to expand...
Click to collapse
Thanks. I posted both the update and your log to the development forum to see if someone with more knowledge can do anything with them.
For the record, pushing that recovery doesn't work. Well, pushing it works, but you can't get into it on the phone. I repushed TWRP to my phone in the interim.

chrisliphart said:
19.8MB update. Can't be too much going on in there, but I'd also think it's more than a few lines of code being updated...
Ooh, fun. Looks like I can't install the OTA with CWM or TWRP. Jonslice, are you rooted?
EDIT:
Weird. Now my phone says the software is up to date. What's the Build info under About Phone for you guys? Wondering if it did actually update even though it said it failed...
Click to expand...
Click to collapse
I got failed update with CWM also. I'll try to post a build info screen shot once I'm on my desktop when my work week is over. Manual check for update says I still need update.
Note: unlocked boot loader, CWM and rooted.
Sent from my HTC first using xda app-developers app

As long as this doesn't remove the ability to disable Facebook Home, I'll probably update it. Can anyone confirm that this is the case?

Daman09 said:
As long as this doesn't remove the ability to disable Facebook Home, I'll probably update it. Can anyone confirm that this is the case?
Click to expand...
Click to collapse
That's a feature of Home, not the firmware. So yeah, you can still disable it. I don't ever see even Facebook changing that.

[Q] Seems like I have the first bricked note 3

So I was messing with the system permissions in Es file exolorer, when I accidently set everyrhing to 666. As soon as I hit back I knew I was done for. I started getting foce closes on everything. I reset the phone hoping I could factory reset and be ok; but it keeps looping back to recovery when I turn it on. Im not home/in front a computer right now....but it seems my only hope is odin with the root files. I havent been able to find a stock rom for this phone. Att sucks for locking the bootloader. I will be donating to the bounty when I get in the house.
Anyone have any suggestions or know where a stock rom is oosted?

hawk915402 said:
So I was messing with the system permissions in Es file exolorer, when I accidently set everyrhing to 666. As soon as I hit back I knew I was done for. I started getting foce closes on everything. I reset the phone hoping I could factory reset and be ok; but it keeps looping back to recovery when I turn it on. Im not home/in front a computer right now....but it seems my only hope is odin with the root files. I havent been able to find a stock rom for this phone. Att sucks for locking the bootloader. I will be donating to the bounty when I get in the house.
Anyone have any suggestions or know where a stock rom is oosted?
Click to expand...
Click to collapse
go to root de la vega site, and download the root. there is an odin image there to restore you to stock. you are ok.

thanks
Thanks a lot. Finally home will try right now

NO GO
Ok so the root de la vega seems to have been taken down since there is a new method. And I cant find the firmware for our phones,
What will happen if I try to load a tmobile firmware to the phone?
At this point I think I have a brick and might try it.

hawk915402 said:
Ok so the root de la vega seems to have been taken down since there is a new method. And I cant find the firmware for our phones,
What will happen if I try to load a tmobile firmware to the phone?
At this point I think I have a brick and might try it.
Click to expand...
Click to collapse
I sent you a PM. Check it quickly!
kraz

Back up
krazman325 said:
I sent you a PM. Check it quickly!
kraz
Click to expand...
Click to collapse
Thanks for the help guys. Im up and running again.

First? No.
I bricked my phone well over 10 times already since the day got it. (Damn you framework-res.apk and androidpolicy.jar )
It's all part of the fun! Glad to hear you're back up and running.
Sent from my SAMSUNG-SM-N900A using Tapatalk

Bricked
Well, I've done it too, but mine brick is probably worse. I updated with OTA update, then attempted to root so I tried flashing the Odin inside the Vega package, just to find out the OTA patched the "holes", now I'm stuck at the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
So I tried the One Click from the Vega package, but it doesn't do it, it fails with write protect error.
Kies don't have emergency recovery either, and won't even recognize the device.
I'm thinking I have to wait for the actual updated one click comes out to fix it.
Please be warned, DON'T try it

ebaul said:
Well, I've done it too, but mine brick is probably worse. I updated with OTA update, then attempted to root so I tried flashing the Odin inside the Vega package, just to find out the OTA patched the "holes", now I'm stuck at the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
So I tried the One Click from the Vega package, but it doesn't do it, it fails with write protect error.
Kies don't have emergency recovery either, and won't even recognize the device.
I'm thinking I have to wait for the actual updated one click comes out to fix it.
Please be warned, DON'T try it
Click to expand...
Click to collapse
There are quite a few of us in that situation. There are a number of people working on it. Hopefully something will come up soon. I wish AT&T would actually release official firmware for our phone through Kies. Would make the recovery process so much faster than having to wait for people to rip MJ5 and re-package it.

i get a black screen....Help
i went ahead and rooted with kingo and deleted some stuff in the system/app folder and now after reboot i get com.google.process.gapps, dropbox, setup wizard and chaton [ unfortunately process has stop ] and it goes into a reboot loop, i can stop the reboot loop when i reroot with kingo but then all i get is a black screen with no apps, launcher, no access to any applications other than the systems settings. Pls help...

fuuhhhh!!!
Me too - figured I'd wait a week before rooting, didn't even bothering to check xda, my bible on such matters, and her I am thinking I know better.
... neeeds me phooooooneeee!!!!!!!!