Related
Rooted removed oclf. Updated. Pissed.
Progress bar got to 53% then said download failed. Reebooting. Vibrant screen. That's it.
Ditto...
this is BS
call tmobile.. post on their website..
I'm not touching this update with a ten foot pole. More headaches than it's worth. I'm honestly getting very close to the point of throwing my Vibrant up on Craig's List and heading the way of the G2... . I love this phone but the software support is just horrendous.
Update went smooth for me, although I used Odin to flash stock JFD back a couple days ago from custom kernel. All I did since update was root.
Were you stock JFD or something other, ie kernel change etc...
where did you get your stock from
I was still jfd. Tpain is sending another phone.
Worked fine for me but I dont use custom roms either. I just have ryans one click lag fix going with launcher pro plus and root.
Gps worked flawlessly, the task manager they put in is pretty robust, and the swype voice recognition is working wonderfully. I think I may be seeing a speed increase? Not exactly sure about that.
Sent from my SGH-T959 using XDA App
same here. went to t-mobile store and got a borrow phone. -___-'
I want to know if a completely stock phone safe to update, i know there may be tons of the same Q/A, but there is too many post that can't find.
I have one and updated without any problem, my GF one doesn't showup and update yet, but want to make sure before she press yes
ota bricked me too
same as above updated to 53% said update failed rebooted to virant screen and nothing . now have loaner cant get new vibrant till tues.
For everyone who had stock kernel + root, can you list what else you might have had installed on your system that could compromise the OTA?
Spotty connection?
Low battery?
Connectivity only over wi-fi at during update?
ROM manager?
Titanium Backup?
Bricked my phone stock with root. It completed the full install rebooted and hung on the vibrant screen for over an hour. I also have a loaner phone (just found my G1 thank god) and I'm awaiting a replacement.
As for changes made:
- full battery
- signal connection (3G two bars)
- Rom Manager Installed
- Titanium Backup Installed
- Removed T-mobile boot images and sounds
I'm going to try to update my phone through Odin and see if I can bring some life back to it. I'll let you know how it goes.
How to fix your phone and apply the update:http://forum.xda-developers.com/showthread.php?t=803492
So should I update then root with the new phone when it comes?
ntellegence said:
So should I update then root with the new phone when it comes?
Click to expand...
Click to collapse
You can Odin JI6 tarball. Then you can use the old update.zip method to re-root the phone.
It's working fine for me. Going to check the GPS out later (I'm inside right now), but the compass is a little herky-jerky so far.
BritCrit said:
As for changes made:
- full battery
- signal connection (3G two bars)
- Rom Manager Installed
- Titanium Backup Installed
- Removed T-mobile boot images and sounds
I'm going to try to update my phone through Odin and see if I can bring some life back to it. I'll let you know how it goes.
Click to expand...
Click to collapse
Points of commonality is Titanium + Rom Manager + renamed boot sounds (I left my boot images intact).
My battery was 78% and I was on over Wi-Fi.
My phone bricked too...Pretty sure it got to something like 53% - wasn't paying attention, but it looked like half way on the progress bar, then next thing I saw was the Vibrant screen.
I was rooted, with Titanium and Rom Manager and the battery icons...
TMobile is sending me a new phone, so I'm gonna try to fix this one first and see if the steps above work...if so good, I can't wait 7 days for a phone. It seemed pretty easy to get a replacement though. Like maybe this was common with this update?
jmerchant said:
I was rooted, with Titanium and Rom Manager and the battery icons...
Click to expand...
Click to collapse
I don't think rooting affects the update, but in order to install both of these apps you need root. Titanium installs busybox which supports LZO and ROM manager installs Recovery. I'm wondering if either of those would affect the OTA update.
Hey folks, I've read through all the JI6 OTA threads here and on the TMo forums and while I've seen a few people guess as to the cause of soft bricks, dosen't seem like anyone has nailed down the actual cause. I'm going to assume I'm not the only person out there with no access to a windows box to run ODIN so knowing what if anything can be done to prep my phone before accepting the OTA (that is sitting in my notification bar as we speak) would be immensely helpful.
So far the two best guesses I've seen are the existence of other update.zip files on SD and removal of bloatware, specifically Media Hub and possibly edited startup/shutdown screens.
Since I've got all these going on, I guess I'm staring down the barrel of a brick. But obviously one of these is easily rectified while the others, not so much.
Aside from those claiming bricks on vigin phones. Can we hear from those who have made mods to their rooted devices and either did or did not experience an OTA brick? I think this info will be helpful to many in sorting out what exactly is going on here.
I have black bar mod, I have naked swype, removed most t-mob app except media hub no change to start up or shut downtried to update. 50 % through it said update failed. Then rebooted fine. But I had an extra update.zip on my sd so maybe that's why. But no firmware now? Maybe I'm sol.
Sent from my SGH-T959 using XDA App
Mine wouldn't complete the update Rooted, most of the bloat removed, had an update on the sd. Was able to get into clockwork after the failed update and am performing a nandroid restore now.
this is great, thank you. beginning to look more like an issue with extra update.zip files than media hub. any successful OTA's with media hub removed prior to accepting the update?
Sent from my SGH-T959 using XDA App
I never uninstalled Media Hub. I have seen a correlation of about 5 people who had ROM manager installed and used that to install Recovery. Whether it be the installation of Recovery or a possible permissions issue with how it generates the update.zip that may have caused my issue.
just a question, why do people remove media hub? Does the application make the phone slow?
iynfynity said:
just a question, why do people remove media hub? Does the application make the phone slow?
Click to expand...
Click to collapse
Because up until now, it was a non-functional app. I didn't remove it, I use LauncherPro so I just removed it from my drawer. I'm still not touching this update. I got my Vibrant used so I would be out of luck if it jacked my phone up and I hate using ODIN. Too much hassle when my phone runs great on Bionix 1.4 as it is.
Wife's phone was toasted by OTA. Stuck at Vibrant screen. Rooted, unlocked, she did have an update.zip, if that turns out to be the culprit. Also had some apps removed, replacement startup animations, and removed shutdown junk.
She was set for always-on WiFi, too.
My rooted Vibrant soft bricked yesterday and I had to flash stock with Odin. I had the (what seems to be infamous) update.zip, removed Kindle, Mobi TV, Avatar Icon, Gogo. I had RyanZAOneClickLagFixV1+ installed but removed it. I also had the EXT2 Tools installed. @ the time of the update I was @ work and had a full charge on the phone. I flashed back to stock last night after work, and I haven't recieved the update notificaiton again...maybe TMo crossed me off some type of "update list"?
There are also different possible symptoms.
In my case the update appeared to have completed its cycle, except the tail end of the download of the new update wnt really fast then the system rebooted. System came back up into the Black Vibrant screen. I could start 'adb logcat' and the system had SurfaceFlinger repeatedly crashing.
Attempts in Recovery Mode after this to reinstall files didn't resolve the issue, reboots would still lead to a crashing SurfaceFlinger.
2 separate users in a thread, 1 had removed Boot Animations + Sounds, I only had removed Sounds.
Quite a few people had Stock Roms + Root, but some with Root didn't have any issues. Only correlation was with Titanium + Rom Manager, which a lot of people would have installed since it's listed in the Tips and Tricks thread. Titanium shouldn't do anything to the system unless you generate a backup Update.zip or install LZO support busybox.
One guess is that ROM Manager and Titanium can create a update.zip file that doesn't have the proper permissions. An OTA update that attempts to overwrite this file may get confused. Simply removing the file in advance may alleviate this issue. Another issue is ROM Manager installs ROM Recovery, which may change how the OTA perceives the phone.
Bionix 1.4...
I was running Bionix 1.4 KK OC/UV yesterday morning... Was a little dumbfounded when I received the update message from Tmo. Figured it wouldn't show w/ modded handset. Delayed install until I could read everything on here about it. Tried installing over Bionix last night just to see, and had no joy. I had removed all crapware, mediahub included. Hit 50%, said flash failed, rebooted and was back to my homescreen in no time. No ill effects to phone except being denied upgrade.
So I Odined back to Stock JFD FW (and wiped device for S&G), rooted, and updated from JI6 tar posted. Flashed perfectly, no ill effects as I've noticed. Reception is improved (for me anyway), and GPS functions similar to Bionix... No real incentive for update, but was curious.
I see Bionix 1.7 updated so it was all for nothing.
Now to play with other stuff...
Cheers
My girl friends phone bricked the other night from the OTA, it's rooted(update.zip) and has the bloatware uninstalled, nothing else like lagfix/roms on it etc.
T-Moible is sending her a replacement phone, which im pretty surprised about. Now since we have to send the old phone back so they can check for damage or anything that would void the warrenty.
We get to keep the external SD card(Avatar), now im sure there is a pretty good chance they will find that its been rooted. So we would have to pay $400 they said if its voided.
Now I can't get this phone to boot into download mode or even mount it, so what should I do? I know about ODIN but have never used it, can it mount the phone?
I got the soft brick and had to flash back to stock via Odin and then I flashed the JI6 tar file from the forum. All is working fine now.
I had root but no update.zip file on the sdcard root, had removed startup an shutdown sounds, had used both ROM Manager and Titanium (with LZO compression turned on), and had removed bloatware including the non-functioning Media Hub.
Next time I'll flash back to stock before doing an OTA update.
I am rooted have Titanium backup, ROM Manager, and clockwork mod. I also had an update.zip but I think it was from OCLF not from another source. My update went fine and I'm running without any problems on the new update.
PepeLasNoches said:
My girl friends phone bricked the other night from the OTA, it's rooted(update.zip) and has the bloatware uninstalled, nothing else like lagfix/roms on it etc.
T-Moible is sending her a replacement phone, which im pretty surprised about. Now since we have to send the old phone back so they can check for damage or anything that would void the warrenty.
We get to keep the external SD card(Avatar), now im sure there is a pretty good chance they will find that its been rooted. So we would have to pay $400 they said if its voided.
Now I can't get this phone to boot into download mode or even mount it, so what should I do? I know about ODIN but have never used it, can it mount the phone?
Click to expand...
Click to collapse
Woo, got it unbricked! finally got into download mode and ODIN saved the day.
this video was helpful for me: http://www.youtube.com/watch?v=AnY7P14JSWQ
^ODIN walkthrough
paxton said:
I'm going to assume I'm not the only person out there with no access to a windows box to run ODIN
Click to expand...
Click to collapse
there is a cross platform tool being developed called 'Heimdall'. It is currently a command line tool and is in beta. however people are successfully flashing their phones using it. It is obviously not a 'one click' solution, so you will have to go find the proper files and type out the command.
It can be found here http://forum.xda-developers.com/showthread.php?t=755265#
If you are the type of person with access to both a windows machine and a linux machine, I suggest you check this out. Testers are needed. Of course you can test if you don't have windows, but it's nice to have Odin as a back up. ;-) just incase....
-p
I had a failed update twice using Odin. It wasn't until I went back to stock T959JFD for the second time and deleted update.zip and all clockwork back ups that it finally worked. Runs perfect with no issues.
Sent from my SGH-T959 using XDA App
Was rooted with OCLF, Captive camera, gps fix, rom manager, titanium backup and add removal. Removed the OCLF and unrooted, ran the update, looked like it got to 100% (not sure cause I looked away and then back at it right before reboot) but said update failed. Got stuck at the vibrant screen blah blah. I'm pretty sure I had an update.zip on the sd, but not 100% on that. After pushing the update with ODIN I have noticed my phone lagging quite a bit.... Thoughts?
Sent from my Rooted Samsung Vibrant using XDA App
Hello all,
Been rambling around the forums in ninja mode trying to gain enough knowledge to not mess up my phone before trying to mod it but alas best laid plans....
Anyhoo I was working to put the Froyo leak on my phone and everything was good till I did a cwm wipe of the phone and wammo it had problems. I managed to use Odin to get it back to barebones stock, lost my high score in Angry Birds too dang it.
Now that I am back to this point I tried to run the Verizin updates and it downloads and goes into install mode on reboot and it dies at Updating Modem section. At that point I saw I was rooted so I removed that and tried again, no dice amigo. Did a factory wipe, nothing. Cleared the cache, fail again.
If it helps its trying to do a dh12 to di01 update. Got any ideas?
When you went to stock did you flash the stock kernel and stock recovery as well? I had to do this when I updated to dl09
Good question and yes I believe I did, I followed this: http://forum.xda-developers.com/showthread.php?t=782204&highlight=return+stock thread to get the job done. Let me try it one more time.
Also I load the PIT file with each md5 correct?
Looks like I fixed it on the second time around. Not sure what I missed but the update went through. No worries. Might pay someone to hand hold my through getting DL30 on my phone cause even as an IT guy I'm missing something every time.
Strong thing is, once the DI01 update happens it actually doesn't find any other updates...wifi is off.
VZW pulled the DL09 update due to the e911 bug until it is fixed
Makes good sense. Sooo anyone wanna tutorialize me on how to de-crappify my phone? Its worth a donation from me.
You're on di01 right?
I would odin the dl09 package, then use cwm to flash super clean 2.2. Clean, debloated froyo goodness
Sent from my SCH-I500 using XDA App
Sounds good. The problem lies in me somehow fudging up the process at some point and having to set my phone back to stock again.
Where did you see this?
"VZW pulled the DL09 update due to the e911 bug until it is fixed"
Have any sources on this one? I really would like to see them.
Not doubting you, I have just been rebooting and *228 for 3 days trying to get this update only to see this quote...
VZW sent a message to all Fascinate owners the other night acknowledging the bug and a fix being in the works. Why would they continue to push it out after that?
Sent from my SCH-I500 using XDA App
Well...
0123456789
New EA update is being pushed out.
Verizon told me to go to a store as some phones will not accept OTA updates. Seems stupid and like a lie, but whatever...
Atst44 said:
"VZW pulled the DL09 update due to the e911 bug until it is fixed"
Have any sources on this one? I really would like to see them.
Not doubting you, I have just been rebooting and *228 for 3 days trying to get this update only to see this quote...
Click to expand...
Click to collapse
He's right. Google the source if you need it. Please don't take this response as me being snarky, I don't mean it that way.
I think the biggest issue people are having is not being careful and following the directions perfectly.
I was new two days ago and did this with only one hiccup.
1. I followed the Beginner's thread in this forum to get me rooted. First pass with Odin failed as the one click code didn't recognize the phone. 2nd pas worked. Trick was to just turn on USB debugging and plug in phone, do not then click the mount notification. Leave that off as USB debugging was all that was needed.
2. I installed Mod Manager and Titanium backup right after. This was part of the main directions and Titanium (though not mentioned) allowed me to save all my specific apps that had important data, like my 100% completed Angry Birds.
3. I then followed the directions in the developer forum for the How To.. install DL30 for Froyo. This scared me at first because the CW recovery stalled when wiping data. I waited over 30 minutes before getting the courage to pull the battery and start over. Figured its only deleting user data, should be ok. It was and then it worked the 2nd time without fail. I did reboot in normal recovery, but running the update.zip put it back into CW.
4. After that, I rebooted numerous times, checked all stock apps, upgraded firmware in camera, and used Titanium to add back my apps I bought or downloaded as well as restored my bookmarks and memo notes.
In the end I've had no bugs/issues as others have reported. Only functionality not tested is bluetooth as I don't use it for anything.
I hope this helps and if you are walking through it all again, I would be glad to help specific questions based on my experience.
I was DL09 stock OTA at first. I'd recommend getting rooted and using Odin to get the stock DL09 from these forums flashed before you try to put DL30 on. As a developer myself, it just makes sense to always put on builds that are in order of each other. So DI01, then DL09, then DL30.
0123456789
superchunkwii, thanks for the feedback. When I booted into cwm recovery mode it hung too. I think my fatal mistake was I booted in regular recovery mode and did my wipe....sad. I should have just rebooted and went back in cwm like you did.
As far as freezing apps I did not know freezing angry birds would save its data. Boy was my wife is mad (she plays it the most).
I did everything else on cue so I will try again and see how she goes. IT CAN BE TAUGHT! As the genie says.
On another note I did download the EA28 update today, can I install the DL30 Rom or do I need to "downgrade" to DL09 to get this done? Anyone try?
dlmcclou said:
superchunkwii, thanks for the feedback. When I booted into cwm recovery mode it hung too. I think my fatal mistake was I booted in regular recovery mode and did my wipe....sad. I should have just rebooted and went back in cwm like you did.
As far as freezing apps I did not know freezing angry birds would save its data. Boy was my wife is mad (she plays it the most).
I did everything else on cue so I will try again and see how she goes. IT CAN BE TAUGHT! As the genie says.
On another note I did download the EA28 update today, can I install the DL30 Rom or do I need to "downgrade" to DL09 to get this done? Anyone try?
Click to expand...
Click to collapse
1. Not freeze.. that makes it so app won't run. Backup with Titanium Backup is what you need I think.
2. What is EA28? I don't think the fascinate has had that build.
Just got an update EA28 any ideas what it does
Sent from my SCH-I500 using XDA App
EA28 build is the update to fix the emrgency dialing bug in DL09. As I understand, it is otherwise the same as DL09. I am by no means an expert though.
EA28 build is the update to fix the emrgency dialing bug in DL09. As I understand, it is otherwise the same as DL09. I am by no means an expert though.
Click to expand...
Click to collapse
Cool. Can anyone confirm this?
I flashed from TW Bionix-v 1.21 to Trigger 2.1.1 and though the flash went great and the rom seemed to work perfect, my data is all messed up. It seems stuck on E now where before I was always on H. Speedtest has gone from 4000kbps down to 120kbps down. I flashed back to Bionix and even flashed in the KA6 modem that I had the best results with before and the problem still persists. In Boinix it will show the data speed as H, but as soon as I try to access the internet or use Speedtest, it drops to G, then to E. I'm lost as to where to go from here. Any help is greatly appreciated.
What about flashing back to stock using odin then reflashing the rom
Sent from my SGH-T959 using XDA App
Woah, wait up don't flash back to stock or anything. Follow this thread, it has all the modem software in it. I suggest using Odin...it's real simple, just dl the file extract it and load it into the phone section in odin and hit start....BAM you got a new modem. Do tests with JL5, it's a good modem.
I was thinking of flashing back to stock but I've never done it before. Is there anything I need to do differently because of Voodoo? I may just go the AIO Toolbox method if that's ok.
I won't be doing anything until later tonight. I've flashed a few modems in the modem thread, but none have fixed this problem. I may just flash back to stock (I really don't mind), but I'm just nervous about doing it because of having Voodoo on my phone right now. Can I just flash back to stock using the AIO Tools, or is this ill-advised?
Always best to disable lag fixes, I do it even if I don't have to. If the problem is persisting through different modems I dunno what's up....maybe hardware related? Maybe try one of those cell reception mods. That'd be the absolute last thing I'd do though, try every modem if you can.
I really don't know what happened. It may have even been a bad flash with Trigger, that's when things went bad. Honestly I wish I'd have just stayed put with Bionix. The phone was working perfectly with it. Oh well, I think I'll try flashing back to stock, then going back to Bionix.
Try this:
Settings-->Wireless and Network-->Mobile Networks-->Network Mode
I have mine set to WCDMA only. I only use Auto mode when I travel outside of town. Works great and keeps me out of the edge network.
kbohip said:
I was thinking of flashing back to stock but I've never done it before. Is there anything I need to do differently because of Voodoo? I may just go the AIO Toolbox method if that's ok.
Click to expand...
Click to collapse
DUDE, if you haven't ever flashed back to stock, I recommend it now then reflash the new rom. It will totally clean up in ghost data in the phone.
Remember the sequence is Backup everything 1st, then disable the lagfix, Then flash the froyo that does not brick (do not check the repartition box), then flash Stock JFD (this time check the repartition box) Then Root, then, the flash your new rom then Download Rom manager and titanium backup and you are good to go.
BTW, you most likely got a corrupted bit of software in the flash or already it was on the phone but there is no way of knowing, THAT is why you should do this.
kbohip said:
I won't be doing anything until later tonight. I've flashed a few modems in the modem thread, but none have fixed this problem. I may just flash back to stock (I really don't mind), but I'm just nervous about doing it because of having Voodoo on my phone right now. Can I just flash back to stock using the AIO Tools, or is this ill-advised?
Click to expand...
Click to collapse
Sorry to hear that man. I've had this problem before... looong ago. I had just flashed a new release of a TW ROM and all the sudden my data was stuck on E. I was freaking out just like you haha. I odined to stock and reflashed at least 3 times and the problem persisted.
I just left the phone on overnight and it seemed to work itself out by morning. Maybe it was T-Mobile doing maintenance or maybe the phone was just being retarded...
Either way, I'd suggest flashing back to stock at least once to clear things up. Check back in the AM and see if it's fixed or not
oka1 said:
DUDE, if you haven't ever flashed back to stock, I recommend it now then reflash the new rom. It will totally clean up in ghost data in the phone.
Remember the sequence is Backup everything 1st, then disable the lagfix, Then flash the froyo that does not brick (do not check the repartition box), then flash Stock JFD (this time check the repartition box) Then Root, then, the flash your new rom then Download Rom manager and titanium backup and you are good to go.
BTW, you most likely got a corrupted bit of software in the flash or already it was on the phone but there is no way of knowing, THAT is why you should do this.
Click to expand...
Click to collapse
I've never flashed back to stock, and of course all of these excellent custom roms have me flashing like a madman. I think I've flashed at least 5 different roms in the last month at least. I think I understand what you mean by "ghost" data. It's like the old days in Windows 98 where an upgrade install was never as good as a clean install. Flashing back to stock is sort of a clean install for Android I'm guessing?
birgertime said:
Sorry to hear that man. I've had this problem before... looong ago. I had just flashed a new release of a TW ROM and all the sudden my data was stuck on E. I was freaking out just like you haha. I odined to stock and reflashed at least 3 times and the problem persisted.
I just left the phone on overnight and it seemed to work itself out by morning. Maybe it was T-Mobile doing maintenance or maybe the phone was just being retarded...
Either way, I'd suggest flashing back to stock at least once to clear things up. Check back in the AM and see if it's fixed or not
Click to expand...
Click to collapse
Ok, this is strange. It looks like this is exactly what's happening. I'm now getting 4000+kbps down again on H. All day though the phone has been bouncing down to E every time I access the internet, go to market, etc. Upload is still quite a bit lower than it used to be though. Still, in the back of my mind though I feel like what oka said above is probably not a bad idea. For peace of mind I'm going to flash back to stock using AIO Vibrant Toolbox, then root, then flash either Bionix or Trigger back on.
Btw, for the short amount of time I had Trigger installed on my phone, I can tell you that it's a VERY nice rom. It looks great and is at least as fast, if not faster than Bionix. Great, great work.
I was having this problem earlier today too on Bionix. I was downloading Quadrant and I was stuck in E for a couple of hours. Must be something wrong with Bionix. Either way it's working now and I hope you solve your problem!
3g
Sent from my SGH-T959 using XDA App
kbohip said:
I flashed from TW Bionix-v 1.21 to Trigger 2.1.1 and though the flash went great and the rom seemed to work perfect, my data is all messed up. It seems stuck on E now where before I was always on H. Speedtest has gone from 4000kbps down to 120kbps down. I flashed back to Bionix and even flashed in the KA6 modem that I had the best results with before and the problem still persists. In Boinix it will show the data speed as H, but as soon as I try to access the internet or use Speedtest, it drops to G, then to E. I'm lost as to where to go from here. Any help is greatly appreciated.
Click to expand...
Click to collapse
Maybe you did something wrong,i also move from Bionix V to Trigger 2.1 and my data is working well,the only thing i notice is that 3g works like edge now,very slow and when on H it fly.
I've recently flashed NAE modem via Odin 3.09, also flashed Philz latest recovery. I was doing this so i could flash Rawintellects Stock(ish) ROM.... which seemed so badass. Really wish i could have got it working. Anyway, on to the problem.
Firmware flash went fine, Philz reovery went fine, ROM flash went fine. Now... I BELIEVE (can't remember) that i was coming from a MDL firmware, not sure though. After ROM flash, things were glitchy. No wifi (fixed after following suggestions in his thread. No 3g... fixed after a clean wipe 3X's and fresh ROM flash. And NO SOUND... never fixed. I spent half a day trying to get it right, never could.
So I decided to try another ROM, next was Negalites WondROM. Seemed cool, but had all the same issues. Exact same. Locking up, swipe screen locking up. System crashes, random reboots. NO SOUND. Figured, WTF.... tried another ROM same issues. At this point I thought maybe all these ROMS had the same kernal and that was the issue, so i flashed dif kernals compitable and recommended for dif ROMS. ALL SAME ISSUES. From here I figured it was the NAE modem the phone didn't like for whatever reason.
So now I'm stuck. I want to start over, want to flash MDL modem again, want to put the ROM i had back on here (I believe it was BluKuban or something). I am fairly certain there is now ay to take this phone back to the store and have them repair it, they will surely find something that will void the warranty even though im also fairly certain there is no warranty left on the phone. This phone is a business phone on our business account (one of 6 phones) and we've had buisiness with this sprint location for over a decade so i amy be able to persuade a repair.
Need help guys =(
Fixed
Battery below 40 percent made this phone do some wonky things, after being fully charged this morning, i was able to use download mode and flash stock modem and revert all changes and get factory image. Lost root, recovery, and roms. But everything is back to normal.
Got the info i needed to do this from this guys thread, the only other thread that i found with the same symptoms and issues as me: http://forum.xda-developers.com/showthread.php?t=2662491
WOOHOOO!!:good::good:
ograyray said:
Battery below 40 percent made this phone do some wonky things, after being fully charged this morning, i was able to use download mode and flash stock modem and revert all changes and get factory image. Lost root, recovery, and roms. But everything is back to normal.
Got the info i needed to do this from this guys thread, the only other thread that i found with the same symptoms and issues as me: http://forum.xda-developers.com/showthread.php?t=2662491
WOOHOOO!!:good::good:
Click to expand...
Click to collapse
NAE wont work on my phone with any ROM, same issues. MF9 works just fine so I don't bother. You could have just ODIN'ed the modem only rather than losing everything.
tensux said:
NAE wont work on my phone with any ROM, same issues. MF9 works just fine so I don't bother. You could have just ODIN'ed the modem only rather than losing everything.
Click to expand...
Click to collapse
Thanks, at that point I was happy to get anything to work, nothing lost really, just maybe 4 or 5 roms, a few GAPS packages, dealing with realizing I flashed a 4.4.3 image though.... And reading through everything looks like there is no root method available for 4.4.3 yet.... BUT HEY, got the phone functional and usable.
You can still root your phone...nothing you have done is final
Sent from my SPH-L720 using XDA
tensux said:
You can still root your phone...nothing you have done is final
Sent from my SPH-L720 using XDA
Click to expand...
Click to collapse
I like two things. 1. Phone works 2. 4.4.3 is fast and battery life is awesome so far. I do hate the bloatware and bright ass yellow splash screen on boot. But i believe i can stick with this until root for 4.4.3 is out.
Gonna miss my ROMs till then. Unless you can find root method for 4.4. It's out for S5 but not S4. I'd be shocked if i was wrong.
You should read up a bit... No reason you can't be rooted on 4.4.3
Sent from my SPH-L720 using XDA