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
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.
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?
Ok, so before I get flamed, let me say that I did do a search and did see that there are ways to unroot the phone...however, I have what I believe to be a bit of a different case here and am just looking for info before trying any of them.
Background...(this is for a friends phone, not mine, or I would just Odin and call it good. He however does not want to loose any of his settings blah blah blah so doesnt want to go that route unless necessary)...Buddy got his first Epic and had me root it for him (One Click Root 2.5.1), that phone took a **** and had to be replaced. When he took it to Bestbuy (I think there, could be the sprint store, dont know that it matters) they hooked it up to their little file transfer machine, let it do its thing and gave him his new phone. Now, after doing that, it still shows as having Clockwork Mod installed, and you can boot into CWM, but none of the functions work, which I found out when I tried to install EC05 on his phone. I installed the zip to his sd card, rebooted into CWM and selected to install zip from sd...nothing happened...just went to a blank screen and locked up and I had to pull the battery. Rebooted the phone and it went straight to CWM without the three finger grip, I selected to just reboot the phone, lock up and battery pull required. Long story short (I know, too late for that) I tried several options and all of them resulted in a lock up and wouldn't let the phone boot normally...I was really feeling bad thinking that I had actually managed to brick his phone...last thing I tried was the advanced menu and selected to reboot recovery and luckily, that actually worked and booted me into sammys stock recovery mode and I was able to run the zip. Had to reboot several times, but it took and his phone is running well now on EC05.
So now to my question. Since CWM is obviously corrupted on his phone from that transfer and not being properly installed on this phone (I was actually blown away that it transfered in the first place) in order to correct that, do I just apply the newer CWM like its a stock phone and let it try to write over those corrupted/missing files or do I need to try to uninstall what is there first or is he going to be stuck having to Odin and take whatever losses he gets?
Thats actuarry an interesting diremma...
Does the phone show up in adb? Can you SU
Sent from my SPH-D700 using XDA Premium App
If you are rooted still, run MyBackup Root for him and then run Odin. If you're not, run the One Click Root 2.5.5 and then use MyBackup Root.
No, its not still rooted, just showing CWM. Thanks, I will try running 2.5.5 over it. I just wasnt sure if that would cause any problems...will let you know how it goes.
I've had a similar thing happen to me when updating a kernel. Reinstalling the same CWM right over the top worked for me.
I need to send my D2 back to Verizon for a replacement (Keyboard isn't registering presses, double letters, etc.)
I had rooted my D2 originally.
I have pushed the stock SFB to the Phone (Which did not wipe out my apps/settings?)
I then ran Root Checker which returned False, and indicated the folders + files did not exist.
I then did a System Reset, and went back to square one. I re-activated the phone (Did not add any accounts though).
Is there anything else I should do before sending it back to Verizon?
Thanks!
Edit:
On a similar note, What's the difference between an Oxidized and Deoxidzed SBF? Same with System-Only and Full.
(I pushed the Full SBF to the phone, but I'm curious what the other ones are)
Lord Ned said:
I need to send my D2 back to Verizon for a replacement (Keyboard isn't registering presses, double letters, etc.)
I had rooted my D2 originally.
I have pushed the stock SFB to the Phone (Which did not wipe out my apps/settings?)
I then ran Root Checker which returned False, and indicated the folders + files did not exist.
I then did a System Reset, and went back to square one. I re-activated the phone (Did not add any accounts though).
Is there anything else I should do before sending it back to Verizon?
Thanks!
Edit:
On a similar note, What's the difference between an Oxidized and Deoxidzed SBF? Same with System-Only and Full.
(I pushed the Full SBF to the phone, but I'm curious what the other ones are)
Click to expand...
Click to collapse
It didn't delete your apps or data? Interesting. You should have gone into a bootloop after the SBF, requiring you to go into the stock recovery to format system/cache....
As far as odex and deodex'd. Stock ROM's have odex files for every system app installed on the phone. Supposedly they are supposed to help speed up the startup time of the phone.
Deodex'd is obviously when the odex files have been removed, usually to save room in /system and also to allow themeing.
Full SBF includes EVERYTHING the phone came with (ROM, Kernel, Bootloader, Radio, etc.)
System only SBF is only the operating system. You would use this if your not worried about going back to complete stock, and just need to reload the OS.
Hope this has helped!
That's what I thought @ Still had data.
(Unless this process requires an SD card to work, I don't have one in my phone because it's dead )
I flashed it twice, once with the phone on and connected via RSD Lite 4.8, I just selected the phone there, picked the SBF and hit start... It restarted the phone into some boot-loader like menu, said it was recieved a SW Update, restarted itself and... nothing change.
So then I did it again but started it in the boot-loader like menu to no difference, so I just did a factory reset.
Thanks @ Explanation though!
You should be good. Just make sure your system version is 2.3.20 (I think that's the latest version, haven't had a d2 for a while). Make sure your boot logo and boot animation are stock, and that you don't have superuser install.
Sent from my HTC GingerBolt powered by the lastest Synergy ROM
They are indeed stock.
I took my D2 into the store today to see what they had to say, I have no idea if this is truthful or if the guy was just making it up to sound smart (Never can be sure after listening to other people talk about your own field )
Said that the missed keypresses + double repeats I was getting was from the phone having overheated at some point, and the keyboard is coming away from the keys a bit (The rubber mat is 'bubbled' a bit in some spots) were indicators of overheating too.
No idea if this is true or not, but he said warrenty should cover it and I just have to call into Verizon so I'll do that.
I'd have to say the phone would have had to get pretty damned hot to do that, but who knows. As long as warrenty will cover it its all good.
Sent from my HTC GingerBolt powered by the lastest Synergy ROM
I agree... The previous owner might have left it in the sun or something... Did that with my DS, turned itself off but it was fine in the end.
Gonna call Verizon tomorrow, too late now. Thanks for the help!
I'm still curious as to why the full-sbf didn't factory reset it though.
is Root Checker an app?
The Albatross said:
is Root Checker an app?
Click to expand...
Click to collapse
Yes. It attempts to do something that requires Root to do. If it fails, it tells you. It then checks if the superuser app exists and if the folders for root exist.
I have the same problem with double entries on the physical keyboard. I've had my phone for a year and I'm pretty sure I have never had an overheat (and definitely have never left my phone out in the sun). I attributed this to CM7 nightlies, but now I doubt that.
Anyone else have this problem?
Sent from my DROID2 using XDA Premium App
I flashed Stock(ish)v05, played with it for a while, and thought I'd try TriForce5.4. I flashed it, and I really liked the starting from scratch, as I've had my phone for a year or so, and it has a lot of crap on it -- probably good to start fresh.
I installed the essentials, email accounts, facebook, tweetcaster, solitaire megapack and hungry shark evolution.
I think I kind of screwed up installing hungry shark. I had originally installed it on Amazon, and reinstalled it with the play store. No biggie, right? I noticed mainly because the opening animation is different, slightly.
I installed the new google now launcher, and put the games in a folder.
When I played hungry shark - I was surprised to see that it had my app data (I wiped/formatted system/etc) -- I was close to getting a great white, so that was cool. A couple days later -- hungry shark was not in the folder. I went to the play store and it was uninstalled. hmmm. I reinstalled it, and no data -- back to Maco shark. A couple days later -- it wasn't there again. I tried to install it with amazon, but it locked up and wouldn't show it.
I then decided maybe I'd go back to Stock(ish)v05. I went back and proceeded to reinstall stuff. The phone started rebooting randomly. It might seem like a memory error, as it usually happens when installing something. I noticed Stock(ish)v06 was up, so I did a full wipe and went to V06. It had the same problem. After some searching -- I thought maybe there was a modem problem. I odin'd a fresh MK2. Same problem. Any advice? I'm not really a noob, but sometimes have no idea what I'm doing.
CtDMonet said:
I flashed Stock(ish)v05, played with it for a while, and thought I'd try TriForce5.4. I flashed it, and I really liked the starting from scratch, as I've had my phone for a year or so, and it has a lot of crap on it -- probably good to start fresh.
I installed the essentials, email accounts, facebook, tweetcaster, solitaire megapack and hungry shark evolution.
I think I kind of screwed up installing hungry shark. I had originally installed it on Amazon, and reinstalled it with the play store. No biggie, right? I noticed mainly because the opening animation is different, slightly.
I installed the new google now launcher, and put the games in a folder.
When I played hungry shark - I was surprised to see that it had my app data (I wiped/formatted system/etc) -- I was close to getting a great white, so that was cool. A couple days later -- hungry shark was not in the folder. I went to the play store and it was uninstalled. hmmm. I reinstalled it, and no data -- back to Maco shark. A couple days later -- it wasn't there again. I tried to install it with amazon, but it locked up and wouldn't show it.
I then decided maybe I'd go back to Stock(ish)v05. I went back and proceeded to reinstall stuff. The phone started rebooting randomly. It might seem like a memory error, as it usually happens when installing something. I noticed Stock(ish)v06 was up, so I did a full wipe and went to V06. It had the same problem. After some searching -- I thought maybe there was a modem problem. I odin'd a fresh MK2. Same problem. Any advice? I'm not really a noob, but sometimes have no idea what I'm doing.
Click to expand...
Click to collapse
Best bet to clean all the nasties is a complete Odin wipe - grab the full MK2 .tar and flash that. It'll wipe all your partitions and set things right. The tar is here in the forums search a little.
Run Titanium if you want to back up some app data but don't restore any system data.
Fresh MJ2 rom? Stock with root, I assume (no knox) -- which one?
No the super clean tar will have Knox and all bloatware. And no root. You will have to reroot which takes 30 seconds.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
No the super clean tar will have Knox and all bloatware. And no root. You will have to reroot which takes 30 seconds.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I odin'd a stock tar (http://forum.xda-developers.com/showthread.php?p=49213024), and now I'm stuck in the "android is upgrading" screen. I tried a hard reset, data wipe and it still goes to the "android is upgrading..." screen, "starting apps"
Does it make a difference that I was never on a stock MK2? I never updated, I was rooted stock with a bootloader and kept getting the annoying "update downloaded" icon, but never processed it - just ignored it (an occasionally deleted it in file explorer, but it would eventually download again). Help?
CtDMonet said:
I odin'd a stock tar (http://forum.xda-developers.com/showthread.php?p=49213024), and now I'm stuck in the "android is upgrading" screen. I tried a hard reset, data wipe and it still goes to the "android is upgrading..." screen, "starting apps"
Does it make a difference that I was never on a stock MK2? I never updated, I was rooted stock with a bootloader and kept getting the annoying "update downloaded" icon, but never processed it - just ignored it (an occasionally deleted it in file explorer, but it would eventually download again). Help?
Click to expand...
Click to collapse
You didn't brick your device. It turns on and starts to boot it's not dead.
Please go back to here and read through the ENTIRE thread.
Also when you are Odin'ng use version 3.09 (search for it it's here) AND run as administrator.
Power off the phone completely, then go to download mode. Start Odin on your PC then connect your phone to it.
Run Odin.
Many people have used this method to get them back to 'zero' - stock MK2 ROM. You will have to root again - you can use CF-Autoroot or Saferoot; both are here too.
Slow down take your time and do some reading too.
Good luck
leaderbuilder said:
You didn't brick your device. It turns on and starts to boot it's not dead.
Please go back to here and read through the ENTIRE thread.
Also when you are Odin'ng use version 3.09 (search for it it's here) AND run as administrator.
Power off the phone completely, then go to download mode. Start Odin on your PC then connect your phone to it.
Run Odin.
Many people have used this method to get them back to 'zero' - stock MK2 ROM. You will have to root again - you can use CF-Autoroot or Saferoot; both are here too.
Slow down take your time and do some reading too.
Good luck
Click to expand...
Click to collapse
I've done that with odin 3.07 and 3.09 several times. I've downloaded the file several times, wiped-hard reset several times, and still get stuck on boot (sometimes on the pulsing SAMSUNG, sometimes on the Android is updating screen... still no work.
I've seen something about PIT files? Before initiating this process I was having problems with memory which probably initiated trying something new (flash something without bloat -- only install the stuff you use...yadayadayada). I might have had a problem with something there. I keep copying files onto my SD card, and it might have a problem. I'm currently backing up my photos from it to reformat it, and see if that's why I can't copy a ROM to it. Is there a new partition file I can flash? I tried checking that box in odin once, and it errored out.
CtDMonet said:
I've done that with odin 3.07 and 3.09 several times. I've downloaded the file several times, wiped-hard reset several times, and still get stuck on boot (sometimes on the pulsing SAMSUNG, sometimes on the Android is updating screen... still no work.
I've seen something about PIT files? Before initiating this process I was having problems with memory which probably initiated trying something new (flash something without bloat -- only install the stuff you use...yadayadayada). I might have had a problem with something there. I keep copying files onto my SD card, and it might have a problem. I'm currently backing up my photos from it to reformat it, and see if that's why I can't copy a ROM to it. Is there a new partition file I can flash? I tried checking that box in odin once, and it errored out.
Click to expand...
Click to collapse
Do not go the pit route. You'll surely destroy your phone.
Boot to stock recovery and try a factory reset
Sent from my SPH-L720 using XDA Premium 4 mobile app
leaderbuilder said:
Do not go the pit route. You'll surely destroy your phone.
Boot to stock recovery and try a factory reset
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your help....I'm generally pretty handy searching the forums, but this hasn't responded like it should (always hangs - even after factory reset). I found an old TWRP backup, and restored it. It didn't work, as I had already flashed the (unsuccessful) stock MK2, that had already updraded to MK2 (and the old backup was from MF9, I think?). From there I didn't have data, but I could wifi and download the Stock NAE with root (http://forum.xda-developers.com/showthread.php?t=2650706.
I'm dealing with 4 month old text messages and expired passwords, but it is working.....:victory: