Related
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
I am having problem updating to 2.340.
I just got a replacement DX from Verizon few days ago. As soon as I received it, I tried to do an update but the system said that I was up to date even though my software showed 2.315 so I decided to mod my DX right away since most people did not have problem updating with rooted DX.
Initially, I rooted my phone with Z4ROOT, reinstalled all the apps using Titanium Backup which i had on previous phone since I all the backups on my
SD card than I back up the stock ROM with Rom Manager. After that, I installed Bazinga2.1 Rom. Installed my apps again using titanium back up and back it up again using ROM Manager. After this, I installed BigDX blue theme. Couple a days ago, I got a notification that I have an update from Verizon which was 2.34 so I went back to recovery, restored back the Stock, using Z4Root, unrooted and download the 2.34 update and tried to install but the update failed. So I did a factory reset and put every thing back to stock and tried to update again and it still fails.
Once the update is down loaded, I try to install and its turns off the phone, than it shows a box with android next to it and it shows triangle with Exclamation and just reboots. Than it goes to clockwork mod recovery.
Why does my phone go to clockwork recovery even though I am UNROOTED?
Any help or input will be greatly appreciate it.
Thanks
johann718 said:
I am having problem updating to 2.340.
I just got a replacement DX from Verizon few days ago. As soon as I received it, I tried to do an update but the system said that I was up to date even though my software showed 2.315 so I decided to mod my DX right away since most people did not have problem updating with rooted DX.
Initially, I rooted my phone with Z4ROOT, reinstalled all the apps using Titanium Backup which i had on previous phone since I all the backups on my
SD card than I back up the stock ROM with Rom Manager. After that, I installed Bazinga2.1 Rom. Installed my apps again using titanium back up and back it up again using ROM Manager. After this, I installed BigDX blue theme. Couple a days ago, I got a notification that I have an update from Verizon which was 2.34 so I went back to recovery, restored back the Stock, using Z4Root, unrooted and download the 2.34 update and tried to install but the update failed. So I did a factory reset and put every thing back to stock and tried to update again and it still fails.
Once the update is down loaded, I try to install and its turns off the phone, than it shows a box with android next to it and it shows triangle with Exclamation and just reboots. Than it goes to clockwork mod recovery.
Why does my phone go to clockwork recovery even though I am UNROOTED?
Any help or input will be greatly appreciate it.
Thanks
Click to expand...
Click to collapse
Root and the bootstrapper are separate entities. Removing root, and removing the boostrapper manually (by renaming files in the system) will not fix your issue either.
The reason I know this is because I went through a number of ways to try to get the OTA, but could not.
I would suggest you hit MDW and get all of the latest files for the update, and do it that way.
You'll sbf, flash the leak for .320, then sbf .320, then flash the system for .340, then update the kernel, and radio afterwards. After that, you'll be back on the normal track.
It's a lot of steps, I guess, but it really doesn't take long.
Go grab the files ASAP, in case they get pulled, and follow all of the instructions carefully.
Whats MDW and why am I having this problem when everyone else is not. also, I removed Boostraper and it still go into recoverymod? I am just going to SBF reflash to 2.315 and see if it will work.
Here we go again!!!
Lots of people had that issue.
Mdw is mydroidworld.com
Sbf all you like. I stand behind the advice I gave.
Also, if you had actually removed the bootstrap correctly, you couldn't possibly still end up in clockwork.
Either way, in about the time it took you to post, you could have used the steps I suggested and have been done.
Sent from my DROIDX using Tapatalk
I'm in a bit of a hurry so I haven't read the whole thread thoroughly, but if you're just trying to get it to stop booting into CWM, go to terminal emulator
Run "su"
Run "mount -o remount,rw /dev/block/mmcblk1p21 /system"
Run "cp /system/bin/logwrapper.bin /system/bin/logwrapper"
Reboot
bladebarrier said:
Lots of people had that issue.
Mdw is mydroidworld.com
Sbf all you like. I stand behind the advice I gave.
Also, if you had actually removed the bootstrap correctly, you couldn't possibly still end up in clockwork.
Either way, in about the time it took you to post, you could have used the steps I suggested and have been done.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice but I SBF my phone back to 2.315, than tried to do update again and it worked.
I used ODIN to revert back to stock kernel, rooted my vibrant, then I installed rom manager from the market.
However, when I start rom manager and click "Flash ClockworkMod Recovery", nothing actually happens! I don't get prompted to select a phone model or anything. Upon rebooting into recovery, I don't even get to the clockwork mod recovery screen. What gives?
it's driving me nuts and i'm going to set dev's on fire, esp since i just downloaded nero. samsung doesn't seem to be supported with the new update as of the last 24 hours and now i need a new method for getting into clockwork without using terminal or adb of any of that stuff. im not a total noob, but trying to work with that is like trying to read spanish. no comprehendo'
the weird thing is that I was able to use rom manager in the past to go from samsung's stock firmware to Onyx, and again when I went to Nero Beta. I don't understand why it would stop working now.
http://forum.xda-developers.com/showthread.php?p=9869448#post9869448
BAM!!!!! clockwork backdoor confirmed.
installing nero as i type.
^ thanks for sharing the fix. Fyi though, koush has fixed the server issue. All is well.
I just flashed Bonsai rom and I finally have froyo on my epic!
Although I had problem following instructions, I finally got it working.
I'd like share my experience of flashing froyo rom on stock phone in hope to help other people who haven't flashed a rom like me before. Please go easy on me, this was my first time flashing custom rom.
First, I copied Bonsai rom file to sdcard.
Then, I flashed stock DK28 rom using the Odin program. This was very easy to follow and was done very fast. Within minutes, I had stock froyo on my phone.
Next, I downloaded Clockwork MOD v3.0.0.x and follow the direction of installing samsung driver and activated the debugging mode on the phone.
After the computer recognized the phone (it took a while and I had to pull the USB from the phone and back again), I ran the run.bat and clockwork mod was installed.
Now, I had to boot in to recovery mode, which I had problem. I didn't know that I had to fully turn off the phone to boot into recovery mode. After the phone is fully turned off, press volume down, camera button and power button and hold all 3 buttons for while.
Once I was in the recovery mode, it automatically backed up data. This took a while. After that, I wiped data, cache and dalvik cache several times.
Then I installed Bonsai zip file while I was in the recover mode. It automatically installed and rebooted the phone.
But for me something went wrong. The phone had mixed up boot animation, and it booted to stock DK28 theme. Also when I touched the phone, it didn't respond and rebooted. I had to pull the battery and boot to recovery mode.
I then wiped data several times again and reinstalled the Bonsai rom. This time it rebooted correctly! I confirmed by checking the About in the phone.
So far its working good and Quadrant benchmark gives me 1800 range.
Also I am happy that after few tweaks, my stock earphone control is working!
Now I am a happy camper!!
Excellent. Check out the other ROMS when you get the chance.
I too just recently decided to root/new rom my epic. It was extremely easy and not nearly as complicated as I thought it might be. Went with Bonsai also because the instructions were so simple and I wanted a simple functional rom. So much faster and better! Few little nuances, (call log having sms messages which i fixed) and the speakerphone toggle on calls but other then that it is awesome. Anyone on the fence...take the jump.
I think I will take the jump this weekend for the first time. I have wanted to install froyo and try out the many custom roms for a long time now. I guess I'm just a little nervous but I'm sure there is not much to worry about.
Sent from my SPH-D700 using XDA App
i tried a few of the dk28 roms (frankenstein, bonsai, nebula, quantum) over the past week or so, and kept running into hiccups that didn't really entirely kill the enjoyment of having froyo on my epic, but it really soured the deal. i appreciate what the devs have done with the dk29 leak. i'm sure it leaves much to be desired, but i'm looking for a smoother experience so just today i flashed back to syndicate. have to say i'm very pleased with that decision
The reverse is the case for me. No DK28 ROM has been worth it to me in any case (it's not complete/'tis a leak anyway). Got tired of the stop gap performance and went back to DI18 a while ago and it is a breath of fresh air. Like night and day performance/battery wise.
Until official Froyo is out, i'm not interested anymore.
LordLugard said:
The reverse is the case for me. No DK28 ROM has been worth it to me in any case (it's not complete/'tis a leak anyway). Got tired of the stop gap performance and went back to DI18 a while ago and it is a breath of fresh air. Like night and day performance/battery wise.
Until official Froyo is out, i'm not interested anymore.
Click to expand...
Click to collapse
Im in the same situation as you. Ive tried all of the Dk28 roms and always came back to my DI18 set up. Most Dk28 roms worked well overall. However I personally couldnt get over the lag, no matter how small. With my current DI18 rom and kernel set up, everything flies. The devs have done a great job tho on all of the 2.2 roms.
Sent from my SPH-D700 using XDA App
I Rooted my phone.
Installed ClockworkMod rom manager
Tried (numerous) times to do a backup, but it always says "can't mount" or "can't open" and fails.
I've lost my bluetooth and vibrate in the process.
I am (and was already on) EA28 when starting all this.
Can anyone help a confused newbie???
I'm not any idiot, I'm a software developer and ASP.Net web developer. But all this Linux style command line stuff is beyond greek to me...
I'd like to get to the point where I had a known-good backup and could try using the DL30 leak.
I have Odin working on my laptop but have uninstalled "superuser" in an effort to get vibrate and bluetooth working again. As I said, it's a mess.
rvgraham said:
I Rooted my phone.
Installed ClockworkMod rom manager
Tried (numerous) times to do a backup, but it always says "can't mount" or "can't open" and fails.
I've lost my bluetooth and vibrate in the process.
I am (and was already on) EA28 when starting all this.
Can anyone help a confused newbie???
I'm not any idiot, I'm a software developer and ASP.Net web developer. But all this Linux style command line stuff is beyond greek to me...
I'd like to get to the point where I had a known-good backup and could try using the DL30 leak.
I have Odin working on my laptop but have uninstalled "superuser" in an effort to get vibrate and bluetooth working again. As I said, it's a mess.
Click to expand...
Click to collapse
I would follow the "beginners guide" to use the one click root method to get root back. Then flash the stock DL09 that's in the forums using odin to get to a point where you can push DL30 out.
Open ODIN, go get a DL09.md5.tar from the development section,
Take your battery out
Plug in the USB ** While holding Volume Down** (thanks for the save Superchunk)
Once in Download mode add the file to the PDA on Odin
Press start
It will erase EVERYTHING HOWEVER bring you back up and running
Alwasy a good idea to keep that file handy incase this happens again, just re-flash
***Note once you flash DL09 to fix everything, your again NOT Rooted, your back to Stock!!!!
(Just on what i use, i've always rooted my phone using http://forum.androidcentral.com/verizon-fascinate-rooting-roms-hacks/33899-how-root.html)
Linden13 said:
Open ODIN, go get a DL09.md5.tar from the development section,
Take your battery out
Plug in the USB while holding volume down
Once in Download mode add the file to the PDA on Odin
Press start
It will erase EVERYTHING HOWEVER bring you back up and running
Alwasy a good idea to keep that file handy incase this happens again, just re-flash
***Note once you flash DL09 to fix everything, your again NOT Rooted, your back to Stock!!!!
(Just on what i use, i've always rooted my phone using http://forum.androidcentral.com/verizon-fascinate-rooting-roms-hacks/33899-how-root.html)
Click to expand...
Click to collapse
edited with what I believe was missing...
superchunkwii said:
edited with what I believe was missing...
Click to expand...
Click to collapse
GOOD SAVE!!!!!
Thanks!
I'll try that when I get home. Never had DL09, went from DI01 directly to EA28, which seems to be a bit of an orphan.
Following your advice(s), what should I be doing to protect my ability to get back to a state where I can use Verizon's updates when and if I want to?
Bob Graham (Newbie Extraordinaire)
Got it working now....
This thread got me on the right track:
http://forum.xda-developers.com/showthread.php?t=944365
Now I have some issues, if that's the right word. Successfully onto DL30, but one of the last instructions on that files was for installing new_cwm.zip.
I don't see Rom Manager in my apps list, though Superuser is there.
Can I install CWM from the market now, so it will show in my apps? Or will that just corrupt the right one that is there(???) but not visible?
Bob
Cwm its a recovery which is flashed through samsung stock recovery. If you download the proper cwm file (which can be found in the dev section) you can power your phone off, then hold down both the volume up and down buttons, then while holding those buttons press and hold the power button til the samsung logo comes up. Blue text soul come up, which would be the stock recovery. You can then flash the cwm file (which you should have placed on your sd card) via the install .zip option in recovery.
Rom manager of available through the market.
Sent from my SCH-I500 using Tapatalk